next-cache-components

You can mix static and dynamic content by enabling cacheComponents in next.config.ts to switch on Partial Prerendering, then annotating specific components with the 'use cache' directive to selectively cache route segments.

Using the 'use cache' directive for Next.js caching requires enabling cacheComponents in next.config.ts first, then adding the 'use cache' directive to your components to start caching content and enable structured caching patterns.

The best way to invalidate cached Next.js components is using cacheTag to label cached content, then calling updateTag or revalidate to trigger fine-grained invalidation and revalidation strategies for per-route or component-level cache management.

Next.js 16 supports Partial Prerendering with cacheLife by implementing Next.js 16 caching primitives, enforcing safe usage of runtime data with allowed directives to tailor cache lifecycle and invalidation per route or component.

Next.js prerendered routes show stale data when cache invalidation strategies are not properly configured. Use cacheLife to define cache expiration and cacheTag with revalidate to ensure fine-grained control over data freshness.