next-upgrade
Skill3.1k starsChanged 9 months agoMITView on GitHub
Upgrade Next.js to the latest version following official migration guides and codemods
- Installs packages
16 other projects use a version of this, 8 of them edited.
Trending
Quiet since March.about the whole repository
Most recently taken up by
- imMamdouhaboammar/openreviewword for word, first seen Nov 15, 2026
- figueroaignacio/ignaciofigueroa.devedited, first seen Nov 8, 2026
- ever-co/ever-worksedited, first seen Nov 8, 2026
- ever-works/ever-worksedited, first seen Nov 5, 2026
- arkantrust/next-skillsword for word, first seen Oct 20, 2026
- davidanthonyn/claude-skillsword for word, first seen Oct 20, 2026
Who's talking about TheEdoRan/next-safe-action
- vercel/next.js“"Server Actions must be async functions." being reported incorrectly”GitHub · Nov 5, 2024 · 13 reactions
- next-safe-action/next-safe-action“[BUG] `onError` called on redirects if it was called previously”GitHub · Dec 1, 2024 · 7 reactions
- next-safe-action/next-safe-action“[BUG] TypeScript issue with parsedInput in useAction Hook”GitHub · Jun 16, 2024 · 3 reactions
- next-safe-action/next-safe-action“[BUG] Not possible to handle errors that are not instance of Error”GitHub · Jan 10, 2025 · 2 reactions
- airjp73/rvf“Fix zod-form-data schema output type that are using `stripEmpty`”GitHub · Jun 10, 2025 · 1 reactions
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- Nov 5, 2024"Server Actions must be async functions." being reported incorrectly — vercel/next.js13 reactions · 5 comments
- Dec 1, 2024[BUG] `onError` called on redirects if it was called previously — next-safe-action/next-safe-action7 reactions · 4 comments
- Jun 16, 2024[BUG] TypeScript issue with parsedInput in useAction Hook — next-safe-action/next-safe-action3 reactions · 8 comments
- Jan 10, 2025[BUG] Not possible to handle errors that are not instance of Error — next-safe-action/next-safe-action2 reactions · 3 comments
- Jun 10, 2025Fix zod-form-data schema output type that are using `stripEmpty` — airjp73/rvf1 reaction · 4 comments
45 more on GitHub
- May 20, 2025Zod v4 support — next-safe-action/next-safe-action1 reaction · 1 comment
- Feb 19, 2025Fix `zfd.formData` input type — airjp73/rvf1 reaction · 3 comments
- Mar 8, 2024[ASK] Error: Cannot access 'action' before initialization — next-safe-action/next-safe-action1 reaction · 3 comments
- Oct 11, 2023Dist files contain incorrect types — next-safe-action/next-safe-action1 reaction · 2 comments
- Mar 25, 2026Bump next-safe-action from 7.10.8 to 8.1.8 — ChazWyllie/kairofit0 reactions · 1 comment
- Mar 15, 2026chore(deps): bump the npm-dependencies group across 1 directory with 14 updates — startberlin/cockpit0 reactions · 2 comments
- Mar 4, 2026[BUG] `returnValidationErrors` called from middleware catch block throws instead of returning `validationErrors` — next-safe-action/next-safe-action0 reactions
- Mar 1, 2026build(deps): bump next-safe-action from 8.0.11 to 8.1.4 — wuyuan1992/react-components0 reactions · 2 comments
- Mar 1, 2026chore(deps): bump the npm-dependencies group across 1 directory with 12 updates — startberlin/cockpit0 reactions · 2 comments
- Feb 28, 2026Bump next-safe-action from 8.0.11 to 8.1.4 — rifandani/feature-flag0 reactions
- Feb 27, 2026Bump next-safe-action from 8.0.11 to 8.1.4 — joehentges/pendulem0 reactions
- Feb 11, 2026[Module Listing Request]: `nuxt-safe-action` — nuxt/modules0 reactions · 2 comments
- Dec 16, 2025Bump next-safe-action from 7.10.8 to 8.0.11 — hiteshhJ/ticketing-app0 reactions
- Oct 29, 2025Bump next-safe-action from 7.10.2 to 8.0.11 — akunpbhanz-lgtm/starter0 reactions · 1 comment
- Sep 30, 2025Bump next-safe-action from 7.10.8 to 8.0.11 — eersnington/diff00 reactions · 2 comments
- Sep 8, 2025Bump next-safe-action from 8.0.10 to 8.0.11 — joehentges/skyline0 reactions
- Sep 1, 2025[npm dependencies]: Bump next-safe-action from 7.10.8 to 8.0.11 in /src — Smegfi/papago0 reactions
- Sep 1, 2025chore(deps): bump next-safe-action from 8.0.8 to 8.0.11 — Shironex/portfolio0 reactions · 1 comment
- Sep 1, 2025chore: bump the dependencies group with 20 updates — alex289/NextJs-Boilerplate0 reactions · 2 comments
- Aug 25, 2025chore(deps): bump the all group across 1 directory with 94 updates — jaqubowsky/create-nextjs-app0 reactions · 1 comment
- Aug 23, 2025chore: bump the dependencies group with 19 updates — alex289/NextJs-Boilerplate0 reactions · 3 comments
- Aug 18, 2025[npm dependencies]: Bump next-safe-action from 7.10.8 to 8.0.10 in /src — Smegfi/papago0 reactions · 1 comment
- Aug 18, 2025chore(deps): bump the all group with 71 updates — jaqubowsky/create-nextjs-app0 reactions · 2 comments
- Aug 18, 2025chore(deps): bump next-safe-action from 8.0.8 to 8.0.10 — Shironex/portfolio0 reactions · 1 comment
- Aug 1, 2025chore(deps): bump next-safe-action from 8.0.2 to 8.0.8 — rifandani/ai-monorepo0 reactions · 1 comment
- Aug 1, 2025⬆️ Bump next-safe-action from 7.10.4 to 8.0.8 — quantified-uncertainty/squiggle0 reactions · 4 comments
- Jul 28, 2025[npm dependencies]: Bump next-safe-action from 7.10.8 to 8.0.8 in /src — Smegfi/papago0 reactions · 1 comment
- Jul 15, 2025chore(deps): bump next-safe-action from 7.10.4 to 8.0.8 — santosmarco/github-jtgc5e-20 reactions
- Jul 15, 2025Bump the dependencies group with 6 updates — RasengunShotaro/pdcxa0 reactions · 1 comment
- Jun 30, 2025[npm dependencies]: Bump next-safe-action from 7.10.8 to 8.0.7 in /src — Smegfi/papago0 reactions · 1 comment
- Jun 26, 2025Bump the dependencies group with 5 updates — RasengunShotaro/pdcxa0 reactions
- Jun 23, 2025[npm dependencies]: Bump next-safe-action from 7.10.8 to 8.0.4 in /src — Smegfi/papago0 reactions · 1 comment
- Jun 17, 2025chore(deps): bump next-safe-action from 7.10.4 to 8.0.3 — santosmarco/github-jtgc5e-20 reactions · 1 comment
- Jun 16, 2025Bump next-safe-action from 7.10.8 to 8.0.3 — joehentges/skyline0 reactions · 1 comment
- Jun 12, 2025[BUG] throwValidationErrors with overrideErrorMessage not working in v7.10.5 — next-safe-action/next-safe-action0 reactions · 1 comment
- Jun 9, 2025Bump next-safe-action from 7.10.8 to 8.0.2 — joehentges/skyline0 reactions · 1 comment
- Jun 9, 2025chore(deps): bump next-safe-action from 7.10.4 to 8.0.2 — santosmarco/github-jtgc5e-20 reactions · 1 comment
- Jun 9, 2025[npm dependencies]: Bump next-safe-action from 7.10.8 to 8.0.2 in /src — Smegfi/papago0 reactions · 1 comment
- Jun 4, 2025chore(deps): bump next-safe-action from 7.10.4 to 8.0.1 — santosmarco/github-jtgc5e-20 reactions · 1 comment
- Jun 3, 2025chore(deps): bump next-safe-action from 7.10.4 to 8.0.0 — santosmarco/github-jtgc5e-20 reactions · 1 comment
- Jun 3, 2025Bump the dependencies group with 5 updates — RasengunShotaro/pdcxa0 reactions · 1 comment
- Jun 2, 2025Bump next-safe-action from 7.10.8 to 8.0.0 — joehentges/skyline0 reactions · 1 comment
- May 13, 2025chore(deps): bump next-safe-action from 7.10.4 to 7.10.8 — santosmarco/github-jtgc5e-20 reactions · 1 comment
- May 1, 2025chore(deps): bump next-safe-action from 7.10.5 to 7.10.8 — rifandani/ai-monorepo0 reactions · 1 comment
- May 1, 2025⬆️ Bump next-safe-action from 7.10.4 to 7.10.8 — quantified-uncertainty/squiggle0 reactions · 3 comments
Used with
Projects with it also use tailwind-css-patterns, two-factor-authentication-best-practices and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
midudevSkilltailwind-css-patterns
Provides comprehensive Tailwind CSS utility-first styling patterns including responsive design, layout utilities, flexbox, grid, spacing, typography, colors, and modern CSS best practices. Use when styling React/Vue/Svelte components, building responsive layouts, implementing design systems, or optimizing CSS workflow.
Also in 5 projects that use this
lukevellaSkilltwo-factor-authentication-best-practices
This skill provides guidance and enforcement rules for implementing secure two-factor authentication (2FA) using Better Auth's twoFactor plugin.
Also in 3 projects that use this
lukevellaSkillemail-and-password-best-practices
This skill provides guidance and enforcement rules for implementing secure email and password authentication using Better Auth.
Also in 3 projects that use this
xenitV1Skillnodejs-best-practices
Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
Also in 5 projects that use this
xfstudioSkillnodejs-backend-patterns
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.
Also in 5 projects that use this
nicepkgSkilltailwind-v4-shadcn
Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React.
Also in 3 projects that use this
- +1 more from lukevella
Other versions16 projects use a version of this.
Word for word · 8
- midudev/preguntas-entrevista-react★ 7.8k100% same
- kokonut-labs/kokonutui★ 2.3k100% same
- vercel-labs/openreview★ 1.7k100% same
- patinaproject/skills★ 1100% same
- arkantrust/next-skills★ 0100% same
- davidanthonyn/claude-skills★ 0100% same
- dorian-akhs/skills★ 0100% same
- imMamdouhaboammar/openreview★ 0100% same
Edited · 8
- openai/plugins★ 7.8k72% same
- legions-developer/invoicely★ 923100% same
- ever-co/ever-works★ 199100% same
- ever-works/ever-works★ 199100% same
- robotostudio/turbo-start-sanity★ 18670% same
- georgekhananaev/claude-skills-vault★ 3166% same
- figueroaignacio/ignaciofigueroa.dev★ 7100% same
- zebbern/termstack★ 492% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- frontend-designSkill
- next-best-practicesSkill
- next-cache-componentsSkill
- pnpmSkill
- skill-creatorSkill
- tsdownSkill
- turborepoSkill
- vercel-react-best-practicesSkill
- vitestSkill
The file
We split this skill into the rules it gives an agent
5 rules. 2 are common, 0 are distinctive, and 3 are very specific to this project.
2
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Detect current version: Read package.json to identify the current Next.js version and related dependencies (React, React DOM, etc.)
- Common: line 15
Fetch the latest upgrade guide: Use WebFetch to get the official upgrade documentation:
- Common: line 38
Review breaking changes: Check the upgrade guide for manual changes needed:
- Very specific: line 49
Run npm run build to check for build errors
- Very specific: line 50
Run npm run dev and test key functionality
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Upgrade Next.js
Upgrade the current project to the latest Next.js version following official migration guides.
Instructions
- Detect current version: Read
package.jsonto 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:
Common transforms:npx @next/codemod@latest <transform> <path>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 buildto check for build errors - Run
npm run devand test key functionality
- Run
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

