Support for cache components in payload

[paulpopus]

Currently payload doesn't support cache components (prev. dynamicIO) from Nextjs (cacheComponents)

Upvote it here if you want this supported

[Livog]

Big +1 from me. This would unlock Partial Prerendering(PPR) so a route can stay static and cached while only the small dynamic pieces can render dynamiclly. Right now a simple cookie read for a “Sign in / My Profile” button can force the whole page dynamic; with cacheComponents only that button becomes dynamic and the rest stays static. Net effect: faster pages, better cache hit rates, and less server work. Same pattern fits small islands like a cart count, wishlist, or notification bell.

[birdzai]

+1. Cache components seem like a natural fit for an embedded CMS

[mattbolt]

@paulpopus We're very keen for this - given we spent considerable effort upgrading our whole site to use cache components, not realising Payload didn't support it 🤦🏼‍♂️

What are the chances this is likely to make it to the roadmap. Even if its not specifically implementing cache components throughout the backend, but getting a tick that says "cache components doesn't break payload".

[DBryja]

Hey! The Payload team mentioned on Discord that they aim to support cache components in version 4.0. To make use of the work you've already done, you could try enabling experimental: { useCache: true } in your config.

I believe you should be able to keep your <Suspense> boundaries as well, as they shouldn't have a negative impact even without full Dynamic IO functionality (correct me if I'm wrong there, as I'm still exploring this myself). This would allow you to keep your 'use cache' directives in place, so once full support is officially released, you'll only need to update the configuration.

[HappyEmu]

I find it hard to swallow that with a "NextJS-first CMS" neither NextJS 15 PPR (granted, experimental), nor NextJS 16 cache components (which is the successor to PPR/dynamicIO) is supported. So you are forced to use either SSR or static prerendering for everything. Payload local API in server components + seems like such an obvious use case for it not to be on the immediate roadmap, especially given that PPR (Next 15 style) has so many drawbacks with Payload (#14487).

[birdzai]

There is a PR #16020 that s being worked on that will allow the use of cache components in your Next.js frontend. It looks like it's progressing and might soon be available.