ISR revalidatePath, revalidateAll, revalidateTag

[mquandalle]

Describe the problem

Currently the way to force the revalidation of an ISR page is to query the server like this:

GET or HEAD request with x-prerender-revalidate: <token> will force the asset to be re-validated

I have some data that is displayed on all pages of my website, and would like to invalidate all pages when the data is updated. Currently I workaround this issue by redeploying the app, but as this is done frequently I'm interested in a quicker ISR cache invalidation instead.

Describe the proposed solution

The revalidatePath from NextJS would solve my issue assuming I can revalidateAll = () => revalidatePath('/'). NextJS also proposes revalidating by tag using revalidateTag.

Importance

nice to have

[madeleineostoja]

Isn't making a GET/HEAD request to a given path pretty much the same thing as invalidatePath already?

[mquandalle]

Maybe I understood it wrong but I though the idea of this API was to invalidate every routes of a subpath, and consequently revalidatePath('/') would invalidate all routes.

[madeleineostoja]

Ah, that’s a good point, and could also be a blocker for me using ISR. I’d also need a way to bust the whole ISR cache when a user publishes new data.

Could someone from the svelte team weigh in on how this mechanism works?

[leoj3n]

I may have made a duplicate of this issue in #12031 so am sorry as I didn't see this at first, but also would like to add that in #12030 I made a similar docs note that redeploying works as you explained here.

[kpc2]

Being able to use revalidatePath('/') would be fantastic. I have a couple of websites that only need to update when changes occur. Redeploying is relatively slow, even for small websites, but it's the easiest solution for changes that affect every page (such as updates to the navigation bar or footer details).

I would also love to have a revalidateTag option. Currently, I rely on a script I wrote that fetches all relevant blog posts in my DB when a tag or category is renamed. It then makes a HEAD request to each page individually to invalidate them, along with all list pages that link to the tag or category in question. While this solution works, Next.js handles it better because revalidation is performed lazily, triggered by the next page visit. In contrast, my solution is eager, causing many revalidations to happen immediately, which can be wasteful if multiple changes are made in succession that affect the same pages.

[kpc2]

I really hope this gets added. As a work-around, I'm thinking of using a free in-memory storage service to keep a list of pages that need to be rebuilt and use my hook.server.ts to trigger a page regeneration for pages on that list when they are next requested. But that adds complexity such as keeping the list clean from removed/renamed pages routes.