Implement Stale-While-Revalidate caching in Service Worker#375
Implement Stale-While-Revalidate caching in Service Worker#375Animation-EdNum merged 1 commit intomainfrom
Conversation
Transitions the service worker from a strict Cache-First strategy to Stale-While-Revalidate. This resolves the risk of users being stuck with stale CSS/JS assets if developers forget to manually increment the static CACHE_NAME version. The cached file is served instantly, while a background fetch, protected by event.waitUntil(), updates the cache for the next visit. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Implemented a Stale-While-Revalidate caching strategy in
sw.jsto automatically keep cached assets up to date without relying on manual version bumps, ensuring offline PWA functionality while mitigating staleness.PR created automatically by Jules for task 10813770445425700425 started by @Animation-EdNum