en un clic
next-upgrade
// Upgrade Next.js to the latest version following official migration guides and codemods
// Upgrade Next.js to the latest version following official migration guides and codemods
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag
| name | next-upgrade |
| description | Upgrade Next.js to the latest version following official migration guides and codemods |
| argument-hint | [target-version] |
Upgrade the current project to the latest Next.js version following official migration guides.
Detect current version: Read package.json to identify the current Next.js version and related dependencies (React, React DOM, etc.)
Fetch the latest upgrade guide: Use WebFetch to get the official upgrade documentation:
Determine upgrade path: Based on current version, identify which migration steps apply. For major version jumps, upgrade incrementally (e.g., 13 → 14 → 15).
Run codemods first: Next.js provides codemods to automate breaking changes:
npx @next/codemod@latest <transform> <path>
Common transforms:
next-async-request-api - Updates async Request APIs (v15)next-request-geo-ip - Migrates geo/ip properties (v15)next-dynamic-access-named-export - Transforms dynamic imports (v15)Update dependencies: Upgrade Next.js and peer dependencies together:
npm install next@latest react@latest react-dom@latest
Review breaking changes: Check the upgrade guide for manual changes needed:
next.config.jsUpdate TypeScript types (if applicable):
npm install @types/react@latest @types/react-dom@latest
Test the upgrade:
npm run build to check for build errorsnpm run dev and test key functionality