ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Select a Nuxt 3 routeRules caching strategy for dynamic pages whose content changes on a fixed schedule, balancing origin load, SEO, and acceptable staleness. Constraint Nuxt 3.8+ lists experimental swr with a default TTL of 3600 seconds and isr requiring an explicit ttl . Both depend on a Nitro-compatible edge platform; self-hosted Node.js deployments
Stale-While-Revalidate Behavior in Nitro Nuxt utilizes the Nitro server engine to implement route-level caching via routeRules . When configuring a route with swr (stale-while-revalidate), the server is designed to serve a cached response immediately while triggering a background refresh if the TTL has expired. Granular Invalidation Constraints While the swr
Cache Synchronization in Hybrid Rendering Nuxt 3 (v3.8+) utilizes Nitro route rules to implement stale-while-revalidate (SWR) patterns via maxAge and staleMaxAge . While this manages the server-side response freshness, client-side data fetching via useFetch or useAsyncData operates under a separate deduplication and payload caching mechanism. In hybrid rende
Nitro Route-Rule Cache Behavior When utilizing swr or isr within Nuxt 3 route rules, Nitro is designed to serve a cached response while triggering a background revalidation. If the origin fails during this revalidation process, the system continues to serve the previously cached version to avoid surfacing a 5xx error to the end user. Consistency in Multi-Rep
nuxtjs
nuxt