next-upgrade

★ 209

by vercel-labs · part of vercel-labs/vercel-plugin

Upgrade Next.js to the latest version following official migration guides and codemods. Use when upgrading Next.js versions, running codemods, or migrating between major releases.

🔌 This skill ships inside the vercel plugin — install the plugin and you also get 5 slash commands, 3 sub-agents, hooks, an MCP server.

This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.

Upgrade Next.js

Upgrade the current project to the latest Next.js version following official migration guides.

Instructions

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:
- Codemods: https://nextjs.org/docs/app/guides/upgrading/codemods
- Version-specific guides (adjust version as needed):
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:
- API changes (e.g., async params in v15)
- Configuration changes in next.config.js
- Deprecated features being removed

Update TypeScript types (if applicable):

npm install @types/react@latest @types/react-dom@latest

Test the upgrade:
- Run npm run build to check for build errors
- Run npm run dev and test key functionality