Development Skill
Angular Migration
Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and…
$15
Next Upgrade
Upgrade Next.js to the latest version with codemods and migration guides.
A risk-minimized playbook for upgrading Next.js across major versions (13 → 14 → 15 → 16) using an incremental, codemod-first strategy. It automates breaking-change migrations like the async Request API, manages peer-dependency compatibility, and verifies each step with type-check, build, and live preview before touching production. Turn a dreaded 'big bang' upgrade into a series of small, reversible, git-committed steps.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category Development
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Version jumps are walked, not leapt. A 13-to-16 upgrade runs as four separate hops, each with its own codemods, its own build check and its own commit.
- Detects the upgrade path from package.json and refuses to jump majors in one leap: 13 to 16 runs as 13-14-15-16, each hop with its own codemods, its own build verification and its own git commit.
- Prepares reversibility before touching code: a dedicated upgrade branch, package.json and lockfile backups, and a known 3-command rollback (checkout main, wipe node_modules and .next, reinstall).
- Runs the official codemods first and reviews the diff: next-async-request-api converts 50+ files in one command, then a targeted grep hunts the edge cases the codemod cannot see (conditional params, wrapper functions) for manual fixes only.
- Updates dependencies as a compatibility matrix, not one by one: next, react, react-dom, @types and eslint-config-next move together (Next 15 hard-requires React 19), and npm ls flags every peer warning as a potential runtime error.
- Walks the manual breaking-change checklist per version: async params/cookies/headers in v15, the fetch cache default flip from force-cache to no-store, Turbopack and Cache Components in v16.
- Gates the release: tsc with zero errors, lint, production build, then a Vercel preview deploy where homepage, a dynamic route, an API route and the middleware are exercised, with a Lighthouse regression check before main merge.
One power source. 6 lines out.
next-upgrade · core
core active · 6 lines
- ✓ jumping from next.js 14
Jumping from Next.js 14 to 15 with React 19
- ✓ adopting next.js 16 cache
Adopting Next.js 16 Cache Components and stable Turbopack
- ✓ migrating sync params/co…
Migrating sync params/cookies/headers to async (v15)
- ✓ resolving peer-dependenc…
Resolving peer-dependency conflicts (next-intl, next-auth, Tailwind v4)
- ✓ clearing deprecated-api…
Clearing deprecated-API warnings from Vercel build logs
- ✓ applying security patches
Applying security patches via clean minor upgrades
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Zero-downtime production upgrades with instant rollback paths
license: perpetual -
Hours of manual editing collapsed into single codemod commands
license: perpetual -
Each version step isolated and verified before the next begins
license: perpetual -
Compatibility surprises caught before deploy, not after
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
8-step upgrade workflow from version detection to runtime test
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
For teams running production Next.js apps who need to move to the latest version without breaking live traffic.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
We're two major versions behind. Do we jump straight to 16 or go step by step?
Step by step, that's the core of the playbook. Each major version (13 to 14 to 15 to 16) is an isolated, git-committed step verified with type-check, build, and live preview before the next begins. The version-specific breaking-change checklists exist per step, so a direct leap would skip the safety they provide.
-
What do the codemods handle, and what's left for me to do by hand?
The official @next/codemod commands automate the mechanical breaking changes, async-request-api, dynamic access, geo/ip migrations, collapsing hours of edits into single commands. What stays manual is peer-dependency reconciliation (next-intl, next-auth, Tailwind v4), guided by the compatibility matrix rather than auto-fixed.
-
Is zero-downtime actually guaranteed?
No, no upgrade process can promise that. The playbook minimizes risk with verification gates at every step and a 3-command rollback path so a bad step is reversible in minutes. Exotic custom code or unusual dependencies can still surprise you, which is exactly why nothing reaches production unverified.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.