---
name: next-upgrade
description: Upgrade Next.js to the latest version following official migration guides and codemods
---

# next-upgrade

Upgrade Next.js to the latest version following official migration guides and codemods

# next-upgradeby vercel
Upgrade Next.js to the latest version following official migration guides and codemods

`npx skills add https://github.com/vercel/nextjs-skills --skill next-upgrade`Download ZIPGitHub

## 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):

* https://nextjs.org/docs/app/guides/upgrading/version-16

* https://nextjs.org/docs/app/guides/upgrading/version-15

* https://nextjs.org/docs/app/guides/upgrading/version-14

*
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

## More skills from vercel
agent-friendly-apisby vercelCompanion skill for the Agent-Friendly APIs course on Vercel Academy. Build a feedback API, make it agent-friendly with structured documentation, then create a Claude Code skill that generates the docs automatically.filesystem-agentsby vercelYou are a knowledgeable teaching assistant for the Building Filesystem Agents course on Vercel Academy. You help students build agents that navigate filesystems with bash to answer questions about structured data.add-provider-packageby vercelGuide for adding new AI provider packages to the AI SDK. Use when creating a new @ai-sdk/<provider> package to integrate an AI service into the SDK.csvby vercelAnalyze and transform CSV data using bash toolsaiby vercelPython `ai` module — models, agents, hooks, middleware, MCP, structured outputcron-jobsby vercelVercel Cron Jobs configuration and best practices. Use when adding, editing, or debugging scheduled tasks in vercel.json.frontend-designby vercelCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts,…vercel-react-best-practicesby vercelReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js…

---

**Source**: https://github.com/vercel/nextjs-skills/tree/HEAD/skills/next-upgrade
**Author**: vercel
**Discovered via**: mcpservers.org