Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

fix(next/image): preserve deprecated prop annotations on Image

Closed Beginner friendly
#3,887 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #4177 by @MumuTW — merged

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
next.js, typescript, vite
Domain
frontend

Research direction

Find vinext’s next/image type definition and compare its ImageProps declaration with the upstream commit linked in the issue. Update the type surface to preserve inherited @deprecated annotations, then check that the editor or TypeScript reports those annotations for image attributes used through next/image.

Written by the indexing model from the issue text.

Description

nextjs-tracking

Upstream commit: https://github.com/vercel/next.js/commit/af44b74d0c948c619330b23dfd3c748657655f11

Next.js changed ImageProps from an Omit<...> & { ... } type alias to an interface extending the same omitted intrinsic image props. This lets TypeScript surface @deprecated annotations inherited from image attributes to users of next/image.

Update vinext's next/image type surface to preserve this editor/type-checker behavior.

Dominant language
TypeScript
Stars
9.2k
Forks
449
Avg merge
22h 16m
Merged PRs (30d)
470

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudflare/vinext

All issues in cloudflare/vinext

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.