next-upgrade

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

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/sharad07072007/paras --skill next-upgrade-sharad07072007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-upgrade
Source: https://github.com/sharad07072007/paras/tree/main/.agents/plugins/vercel/skills/next-upgrade
Command: npx skills add https://github.com/sharad07072007/paras --skill next-upgrade-sharad07072007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Upgrading Next.js across major versions involves breaking API changes, deprecated features, and dependency conflicts that are tedious and error-prone to handle manually. ## Core Features & Use Cases - Guided upgrade path: Detects the current Next.js version from package.json and determines the correct incremental migration steps for major version jumps. - Automated codemods: Runs official @next/codemod transforms such as next-async-request-api to apply breaking changes automatically. - Dependency and type updates: Upgrades next, react, react-dom, and TypeScript type packages together, then validates the result with build and dev server checks. - Use Case: A project on Next.js 13 needs to reach the latest release; the skill walks through versions 14 and 15 incrementally, applying codemods and reviewing breaking changes at each step. ## Quick Start Upgrade my Next.js project to the latest version and run the appropriate codemods.

Frequently Asked Questions about next-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade Next.js to the latest version?

Detect your current version in package.json, follow the official upgrade guides at nextjs.org, run @next/codemod transforms for breaking changes, then update next, react, and react-dom together. Verify with npm run build and npm run dev.

How to run Next.js codemods for breaking changes?

Run npx @next/codemod@latest <transform> <path> with the transform matching your target version. Common transforms include next-async-request-api, next-request-geo-ip, and next-dynamic-access-named-export for v15 migrations.

Can I upgrade Next.js across multiple major versions at once?

Major version jumps should be done incrementally, such as 13 to 14 to 15, rather than skipping versions. Each step applies its own codemods and breaking-change reviews, reducing the risk of compounding migration errors.

Does upgrading Next.js require updating React and TypeScript types?

Yes, Next.js and its peer dependencies should be upgraded together using npm install next@latest react@latest react-dom@latest. TypeScript projects also need @types/react and @types/react-dom updated to matching versions.

Why does my Next.js build fail after a version upgrade?

Build failures after upgrades usually come from unapplied breaking changes such as async request APIs in v15, outdated next.config.js options, or removed deprecated features. Check the version-specific upgrade guide and run the relevant codemods.