ISR in AppRouter

[mjarosch]

Description

With Page Router, we were able to use Environment Variables to set the revalidation time in getStaticProps. With the switch to App Router, you can add export const revalidate = [value]; to the page, but it needs to be a hard coded value. If you use fetch on the page, which I assume happens in the CSDK call on the page, you can set it there with a variable value. Are there thoughts or plans on how to support ISR in AppRouter?

Additional information

No response

[art-alexeyenko]

@mjarosch to make sure I understand the question correctly: you're asking if there is, or will be, a mechanism to configure revalidation on the fly via an environment value (as it was in Pages router). Is that correct?

Generally speaking, our plans for ISR is to make Next JS's tag-based revalidation work nicely with Content SDK, allowing for more precise content regeneration. Cache components support is already present with next 16 upgrade, and this will be the follow up.

[mjarosch]

Yes. We have a "preview" environment that uses the Preview context id for pulling content. This environment is used content authors to preview changes and share changes with other areas for feedback and approval. When we were on the Pages router, we had the ISR interval set to a low value, so that the changes would appear soon after they were made. On our live site, we used a higher value.

Thank you for the response, looking forward to the changes.