Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix Docs: different versions of the same codemods in different places [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#85680•Fetched 2026-04-08 02:14:24
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Git-I985Git-I985
Participants
Git-I985Git-I985icyJosephicyJoseph
Assignees
Git-I985Git-I985
Timeline (top)
renamed ×2assigned ×1commented ×1cross-referenced ×1

Fix Action

Fixed

PR fix notes

PR #85681: docs: align codemods versions

Description (problem / solution / changelog)

Aligned all @next/codemod versions in the documentation

#85680

Changed files

  • .devcontainer/devcontainer-lock.json (modified, +1/-1)
  • docs/01-app/01-getting-started/01-installation.mdx (modified, +1/-1)
  • docs/01-app/02-guides/upgrading/codemods.mdx (modified, +1/-1)
  • docs/01-app/02-guides/upgrading/version-15.mdx (modified, +1/-1)
  • docs/01-app/02-guides/upgrading/version-16.mdx (modified, +2/-2)
  • docs/01-app/03-api-reference/03-file-conventions/proxy.mdx (modified, +1/-1)
  • errors/middleware-to-proxy.mdx (modified, +1/-1)
  • errors/sync-dynamic-apis.mdx (modified, +1/-1)

Code Example

npx @next/codemod@canary middleware-to-proxy .

---

npx @next/codemod@latest middleware-to-proxy .
RAW_BUFFERClick to expand / collapse

What is the documentation issue?

In the docs example, the command uses @next/codemod@canary, but the stable @latest is already available and works fine — so canary isn’t necessary.

Other examples (for 16 version also) on the same page use @latest, so this one should be updated for consistency.

@canary in general used in these places

I dont understand reasons, why different examples use different versions of same codemods, if it was intentional, please please clarify why. It looks inconsistent.

E.g. here, codemod middleware-to-proxy

errors/middleware-to-proxy.mdx

npx @next/codemod@canary middleware-to-proxy .

docs/01-app/02-guides/upgrading/codemods.mdx

npx @next/codemod@latest middleware-to-proxy .

extent analysis

TL;DR

Update the documentation to use @next/codemod@latest instead of @next/codemod@canary for consistency.

Guidance

  • Review the documentation examples to ensure they are using the same version of @next/codemod for consistency.
  • Verify that using @next/codemod@latest does not introduce any issues or errors.
  • Update the command in the documentation to use @next/codemod@latest, for example: npx @next/codemod@latest middleware-to-proxy .
  • Check other places where @next/codemod@canary is used and consider updating them to @next/codemod@latest if possible.

Example

npx @next/codemod@latest next-lint-to-eslint-cli .

Notes

The issue seems to be related to inconsistency in the documentation, and updating to @next/codemod@latest should fix the issue. However, it's essential to verify that this change does not introduce any problems.

Recommendation

Apply workaround: Update the documentation to use @next/codemod@latest for consistency, as the stable version is already available and works fine.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#authentication setup#request error#file not found

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - ✅(Solved) Fix Docs: different versions of the same codemods in different places [1 pull requests, 1 comments, 2 participants]