Narratives Frontend & Frameworks

Next.js 16.4 makes Cache Components the default path for new apps

Built from 2 signals across 2 sources · 111 items reviewed

Next.js 16.4 closes key gaps in its Cache Components model and makes it the recommended choice for every application, moving the framework toward a new default in Next.js 17. New projects created with create-next-app now enable Cache Components by default, while existing codebases get improved migration tooling alongside lazy compilation, smaller Turbopack output, and React 19.3 features.

  • Next.js 16.4 was released on October 6, 2026 as v16.4.0.
  • Cache Components is now recommended for every Next.js app, with new create-next-app projects enabling it by default.
  • The release adds lazy compilation, smaller Turbopack output, Cache Components improvements, and new developer tooling.
  • Next.js 16.4 includes React 19.3 features and improved tooling intended to help existing applications migrate to the new programming model.
  • Cache Components is planned to become the default in Next.js 17, giving teams an early migration window.

Bottom line If you maintain a Next.js application, test 16.4 and its Cache Components migration path before Next.js 17 makes the model the default.

Signals2