Over the 16.x releases, Next.js introduced a new programming model addressing App Router frustrations: fast initial loads, instant client navigations, and opt-in declarative caching. This model, called Cache Components, becomes the default in Next.js 17. Prior to this release, it was not universally recommended due to performance gaps.
Key features in 16.4 close those gaps, allowing Next.js to recommend Cache Components as the best choice for every app. Starting with 16.4, all new apps created with create-next-app have Cache Components enabled by default. Greenfield projects can adopt the model without reservations.
For existing apps, the new `next upgrade --agent` command provides version-specific guidance and dedicated Skills help agents with refactorings needed to adopt Cache Components. 16.4 also includes out-of-the-box improvements for all apps: less memory and disk usage in dev, reduced compile times, smaller production bundles, and React 19.3. Cache Components are a suite of features letting developers mark specific parts of a component tree as eligible for caching. Using 'use cache' annotations, Next.js caches component UI during client navigations and optionally on the server during rendering or build.
These composable annotations mix client-side caching, pluggable server-side caching, and request-time rendering within a single page, replacing implicit caching behaviors of previous App Router versions. A hallmark feature lets pages stream static and dynamic content together in a single server response, enabling sophisticated UIs without sacrificing speed. For fully static pages, the new Static option guarantees a route's shell, prefetch, or navigation is static, preventing dynamic components from accidentally degrading performance or cost characteristics.
Source: Hacker News · Summarized by HeadlinesBriefing