next.js 16 makes turbopack default and swaps middleware for proxy

Next.js 16 changed the default bundler, made caching opt-in and raised version floors, and it is now the only Next.js line in Active LTS.

2025-10-21 release 3 sources · 3 primary 1 min read

// at a glance

version: 16 (latest minor 16.4, 2026-10-06)
requires: Node.js 20.9+ · TypeScript 5.1+ · Safari 16.4+ / Chromium & Firefox 111+
supported until: 16.x Active LTS · 15.x Maintenance LTS · ≤14.x unsupported
platforms: React web apps built on Next.js

what happened

Next.js 16 was published on October 21, 2025.[1]
Turbopack is now the default bundler for all apps. Next.js cites 2–5× faster production builds and up to 10× faster Fast Refresh; webpack is still available with --webpack.[1]
Cache Components, built on the 'use cache' directive, make caching entirely opt-in, so dynamic code runs at request time by default.[1]
proxy.ts replaces middleware.ts and runs on the Node.js runtime. middleware.ts still works for Edge use cases but is deprecated.[1]
Next.js 16 requires Node.js 20.9+ (Node.js 18 is no longer supported), TypeScript 5.1+, and Chrome/Edge/Firefox 111+ or Safari 16.4+.[1]
Breaking removals include AMP support and the next lint command. params, searchParams, cookies() and headers() must now be accessed asynchronously.[1]
Under the support policy, 16.x is Active LTS, 15.x is Maintenance LTS (critical bug fixes and essential security updates only), and 14.x and earlier are unsupported.[2]
Minor releases followed: 16.1 (Dec 18, 2025), 16.2 (Mar 18, 2026), 16.3 (Aug 3, 2026) and 16.4 (Oct 6, 2026).[3]