next-cache-components

Migrate unstable_cache to use cache by applying the use cache directive and defining lifecycles with cacheLife and cacheTag. This update shifts caching into declarative route-level boundaries across your app directories.

Partial prerendering combines static, cached, and dynamic content in a single route. Cache components enable this by applying the use cache directive to isolate cached sections while leaving other sections fully dynamic.

Invalidate cached data by assigning a cacheTag to cached content and calling revalidateTag to trigger refresh. The updateTag function also helps manage cache invalidation lifecycles for robust data freshness.

Yes, cache components apply across both app and src/app directories to manage static, cached, and dynamic content seamlessly. This ensures consistent partial prerendering behavior throughout your Next.js 16 project structure.

Static content prerenders at build time, cached content uses the use cache directive with a defined cacheLife, and dynamic content renders at request time. Cache components combine all three types within a single Next.js route.