next-cache-components

Partial prerendering in Next.js uses cache components to serve a static shell instantly while streaming dynamic sections. You enable it by configuring cacheComponents and using cache directives within your server components for async data.

cacheLife and cacheTag manage cached async data in Next.js by defining expiration durations and invalidation tags. You apply them within use cache directives to control freshness across server components and actions.

The best way to invalidate cached data in Next.js server actions is using updateTag and cacheTag. These tags provide deterministic invalidation, ensuring request handling and data freshness across your production application.

Yes, you can mix static and dynamic rendering in a single Next.js route by using cache components. This allows you to cache repeatable async data like dashboard metrics while streaming user-specific notifications dynamically.

Yes, Next.js partial prerendering requires cacheComponents configuration. This setting enables the use cache directives, cacheLife, and cacheTag needed to combine static, cached, and dynamic content within one route.