Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The inline
// eslint-disable-next-line @next/next/no-img-elementis a pretty broad escape hatch and will likely spread. Since this is a preview of a local blob URL, you can still usenext/imagesafely (it supportsblob:URLs) and avoid disabling the rule.This also gives you better defaults (lazy loading/decoding) and consistent sizing behavior.
Suggestion
Replace the raw
<img>withnext/imageand remove the ESLint disable. Example:Reply with "@CharlieHelps yes please" if you’d like me to add a commit with this change.