I am currently using the workbox-build module, specifically the generateSW mode, to generate my service worker scripts to deploy my web application to Netlify. My site is a static site. Here is my worker-config.js: This configuration works well for online use. However, third party requests to certain assets (i.e. images, Javascript, etc.) are not successfully precached for offline usage. Netlify
Tag: workbox
How to test if Workbox precaching is working
My question is very similar to this question. I’m wondering how I can verify in Google Chrome whether the service worker of my progressive web app is serving precached files from the cache instead of the network. I have a service worker in place which uses following Workbox code to precache some files: I can verify that those files are
Service worker – update cache on new version using skipWaiting()
I have implemented Workbox to generate my service worker using webpack. This works – I can confirm revision is updated in the generated service worker when running “generate-sw”: “workbox inject:manifest”. The problem is – I have noticed my clients are not updating the cache after a new release. Even days after updating the service worker my clients are still caching