With this change, responses from isr routes will be propagated to the global edge network rather than be local to the CDN node that rendered and served it. This will improve performance and reduce serverless function invocations, in various scenarios.
This won't immediately have any effect since we're gradually rolling out the feature on the platform, but by the time nitro v3 (and frameworks that use it, like nuxt v4) are released it should be fully rolled out.
๐ Linked issue
N/A - discussed on Discord
โ Type of change
๐ Description
This is a follow-up to https://github.com/unjs/nitro/pull/2406.
See https://docs.netlify.com/platform/caching/#durable-directive. (This link should go live a bit later today!)
With this change, responses from
isr
routes will be propagated to the global edge network rather than be local to the CDN node that rendered and served it. This will improve performance and reduce serverless function invocations, in various scenarios.This won't immediately have any effect since we're gradually rolling out the feature on the platform, but by the time nitro v3 (and frameworks that use it, like nuxt v4) are released it should be fully rolled out.
๐ Checklist