vercel / vercel/next.js

Docs: different versions of the same codemods in different places

Open
#85,680 1 comment 0 reactions 1 assignee View on GitHub

@Git-I985 is already working on this.

Since Nov 3, 2025.

Dominant language
JavaScript
Stars
142k
Forks
32.4k
Avg merge
2d 14h
Merged PRs (30d)
351

Description

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 .

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.