ISR in partial prerendering

[maral]

Summary

Partial prerendering seems to be a great step forward and I've been playing with ppr and dynamicIO lately. What I can't seem to find anywhere is the ISR in PPR - the ability to invalidate and regenerate the static shell that is part of the PPR. This old blog post hints that this should be possible:

The static shell retains the ability to be updated via Incremental Static Regeneration (ISR).

However, I haven't found any tutorial to do that and my own experiments haven't yielded any success yet. Especially in multi-tenant approach, it doesn't make much sense to generate fully static shells - and even in the PPR demo page it wouldn't be useful as-is - whenever the main product would change, the whole site would have to be rebuilt - instead of a simple regeneration.

So my question is:

• Is this already achievable?
• If not, will ISR be included in the PPR model, and when?

Additional information

No response

Example

No response

[icyJoseph]

I think this is where the use cache set of APIs kicks in - you can read about the bigger picture here, https://nextjs.org/blog/our-journey-with-caching

• https://nextjs.org/docs/app/api-reference/directives/use-cache#use-cache-at-build-time

[maral]

Thanks! I've tested it a bit and it works as I wished - you can make endless combinations of "use cache" and Suspense boundaries. It seems that the shell is for now generated and revalidates based on the shortest cache life in the tree. When I tried using "seconds" for some volatile data, the page itself had Revalidate = 1s. If I got rid of the cache life there, the shell got a better cache life (1m in my case) and the data still loads on each request.

It actually looks pretty cool - however it took me almost a week to find out the direction Next.js is headed in currently. The docs are now a minefield full of various concepts that will be deprecated soon...

[icyJoseph]

Yes, PPR, dynamicIO and use cache are all, in a way, different tracks aimed at solving one specific problem, even if they build upon each other, to some extend. When the time comes and these come out of experimental/canary, and stabilize, we shall have way better docs for them.

[maral]

It's actually really good already - I managed to replicate all the ISR behavior I needed (generateStaticProps, dynamically rendered and cached pages on dynamic route segments...), it works with turbopack, the flexibility in what and how you can cache everything feels great and it's even more intuitive.

When do you think this will all be stable? What about within a year?