StackWatch

Next.js

framework40 releases · 8 support lines

Support lines

LTS status and end of life
LineLatestStatusEnd of life
1616.3.0lts—
1515.5.23ltsends soon21 Oct 2026
1414.2.35ltseol26 Oct 2025
1313.5.11eol21 Dec 2024
1212.3.7eol21 Nov 2022
1111.1.4eol27 Jan 2022
1010.2.3eol15 Jun 2021
99.5.5eol27 Oct 2020

Releases

newest first
Next.jsv16.3.09d agosecuritybreakinglts
  • Fixed a security vulnerability (CVE-2025-13465) in vendored lodash
  • Stabilized several experimental features including instant navigation, app shells, and cache components
  • Enabled Turbopack build filesystem cache and TypeScript CLI by default
  • Improved performance and fixed numerous bugs across rendering, caching, and HMR systems
what breaks

Several experimental features have been stabilized and enabled by default (instant navigation, app shells, cache components, Turbopack filesystem cache, TypeScript CLI), which may change behavior for applications relying on previous defaults or experimental flags. The edge runtime has been deprecated. Some configuration options like experimental.useCache are now deprecated.

to upgrade

Review and test applications using experimental features that are now stabilized. Check if any code relies on the edge runtime (now deprecated) or experimental.useCache (now deprecated). Verify that default behavior changes for instant navigation, app shells, and cache components work as expected in your application.

advisories
CVE-2025-13465
changelog ↗
Next.jsv16.0.013d agobreaking
  • Turbopack is now the default bundler for production builds
  • Partial prerendering left beta and is stable
  • Minimum Node.js version raised to 20.9.0
what breaks

Builds on Node.js below 20.9.0 will fail outright, and any `next/image` usage still passing `layout` stops compiling.

to upgrade

Upgrade Node before upgrading Next. Replace `layout` on `next/image` with the `fill` and `sizes` props.

changelog ↗

← back to the digest