You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
components/pr-stats.tsx renders images with a plain <img>:
lines 265 and 430: member avatars
Plain <img> skips Next.js's resizing, modern formats and lazy-loading, so these avatars download at full size. ESLint flags it (@next/next/no-img-element).
Check it on /pr-stats.
Done when
Every <img> listed above is a next/image<Image> with explicit width/height (or fill inside a sized, relative parent).
Remote hosts are already allowed in next.config.ts (github.com, avatars.githubusercontent.com, images.unsplash.com). If you hit a different host, add it there and say so in the PR.
The page looks the same as before: same size, crop, rounding and hover effects. Add before/after screenshots to the PR.
npx eslint components/pr-stats.tsx shows no @next/next/no-img-element.
npm run build passes.
Size: ~5–15 lines.
Taking this? Comment /assign and the bot assigns you if it's free. One issue per person at a time; comment /unassign to hand it back. That's milestone 2 of the 10 PR Journey. Setup, the checks CI runs, and how to open the PR from your fork are in CONTRIBUTING.md. Put Fixes #<this issue> in your PR description.
Activity