The solution is at hand and has been for some years now as this POC clearly testifies. Unfortunately W3C have fought tooth and nail to prevent it from being made available 🙁 Why? I know not. The “cui bono” argument points to plug-in vendors such as Ionic whose whole raison d’etre appears to be background … Read more
No, you can not. Only one service worker per scope is allowed to be registered so the latest kick the previous one out unless the scope is more specific, in this case, the request is attended by the most specific only. Nevertheless, you can attach multiple fetch handlers and they all will process the request … Read more
In general, code that’s outside any event handler, in the “top-level” of the service worker’s global scope, will run each and every time the service worker thread(/process) is started up. The service worker thread may start (and stop) at arbitrary times, and it’s not tied to the lifetime of the web pages it controlled. (Starting/stopping … Read more
One option is just to use a the service worker’s cache as a fallback, and always attempt to go network-first via a fetch(). You lose some performance gains that a cache-first strategy offers, though. An alternative approach would be to use sw-precache to generate your service worker script as part of your site’s build process. … Read more
The primary difference is control. Browser cache is driven off Cache-Control headers, which is good, until its not. There are all sorts of strategies to manage how network addressable resources are cached; private, public; time to live, etc. With service worker caching you can programmatically control how those assets are persisted. But that means the … Read more
The problem was that the service-worker.js file was stored in an assets sub-directory. Don’t do that: store the service-worker.js in the root of your app (or higher). That way your app can access the service-worker. See HTML5Rocks article — One subtlety with the register method is the location of the service worker file. You’ll notice … Read more
There are conceptually two kinds of updates, and it isn’t clear from your question which we’re talking about, so I’ll cover both. Updating content Eg: The text of a blog post The schedule for an event A social media timeline These will likely be stored in the cache API or IndexedDB. These stores live independently … Read more