Menu
Next.js version migrations using official guides and codemods. Use when migrating a Next.js project to a new major version using codemods.
| name | nextjs-upgrade |
| description | Next.js version migrations using official guides and codemods. Use when migrating a Next.js project to a new major version using codemods. |
| metadata | {"triggers":{"files":["package.json"],"keywords":["next upgrade","migration guide","codemod"]}} |
Automated and manual migration steps for Next.js version upgrades (e.g., v14 to v15).
next, react, react-dom in package.jsonnpx @next/codemod@latest <transform> <path>cookies(), headers(), params awaited (v15+)fetch caching: v15 defaults to no-store; add force-cache where needednext build and fix hydration or Turbopack errorspackage.json for versions of next, react, and react-dom.npx @next/codemod@latest <transform> <path> to automate syntax migration.next-async-request-api transform by ensuring params, searchParams, cookies(), and headers() awaited.react and react-dom to match Next.js peer dependencies (e.g., React 19 for Next.js 15).next dev and next build after each incremental step. Check console errors for hydration warnings.npx @next/codemod@latest transforms first.no-store; audit all fetch calls.export default async function Page() fatal.Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
Turn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.