Should I upgrade to Next.js 16?
Decide when to upgrade to Next.js 16, given Turbopack becoming the default, async request API breaking changes, and official migration guidance.
Not yet — unless you've already migrated off webpack and sync APIs.
Blockers
- Requires runtime/nodejs-20 20.9.0+ (ESM and async API support)
- Requires package/typescript-5 5.1.0+ (type-level features for App Router)
- Requires package/react-19 19.0+ (RSC and async Server Components)
- cookies/headers/params/searchParams/draftMode must be awaited — sync access removed
- next build fails with custom webpack config — must use --webpack flag or remove config
- next lint command removed
- middleware.ts deprecated — renamed to proxy.ts (Edge runtime not supported in proxy)
- framework/nextjs-16 incompatible with engine/webpack: next build fails with webpack config present — Turbopack is default
Who this is for
- small-team
- enterprise
- monorepo
- low-ops
Source-linked facts
Facts updated: 2026-03-15
Published: 2026-03-27
Try with PocketLantern
$ npm install -g pocketlantern # Then ask: $ pocketlantern "Next.js 16 Upgrade: Turbopack Default and Async Request APIs"
Missing something? Request coverage