Skip to content

fix: eslint rule of using img in metadata routes #74864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 14, 2025
Merged

Conversation

huozhi
Copy link
Member

@huozhi huozhi commented Jan 14, 2025

What

Should allow using img tag for metadata routes in eslint rule no-img-element, as it's not a React Component of pages

Fixes #49229

@huozhi huozhi merged commit 958b6b8 into canary Jan 14, 2025
122 of 128 checks passed
@huozhi huozhi deleted the fix/eslint-rule-of-img branch January 14, 2025 16:26
tgv325tgv325 added a commit to tgv325tgv325/next.js that referenced this pull request Jan 20, 2025
@github-actions github-actions bot added the locked label Feb 2, 2025
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[NEXT-1145] Eslint rule @next/next/no-img-element in icon.tsx blocks <img/> but we can't use <Image/> in there.
2 participants