swurl | provide basic curl-like functionality | HTTP library

the solution to my problem was answered in this article about all PWA strategies: https://jakearchibald.com/2014/offline-cookbook/#network-falling-back-to-cache

and what I had to do was add this piece of code to the end of my service-worker.js file:

Here's what you could do.

The trick is to skip waiting for the new service worker.

I adjusted the service worker registration like so:

Apparently, having another service-worker required by Firebase messaging for push notifications were triggering an update everytime.

I honestly didn't mentioned it in the original question because I thought it didn't have anything to do with my problem.

I ended up setting up FCM to use my service worker instead of having it own, and it all started to work properly :)

I can't say much more since I'm not 100% sure WHAT was the problem really, probably the FCM serviceworker wasn't updating itself and made the other one try to update itself everytime? serviceworkers are weird

Use this utility function. It works with a pointer to any type.

navigator.serviceWorker.controller will be set to a truthy value (a ServiceWorker object) if the current page is under the control of a service worker.

If this is the first time a service worker's been registered whose scope encompasses the current page's URL, then navigator.serviceWorker.controller will not be set (unless the service worker itself calls clients.claim()).

If this is a subsequent visit to a page that is under the registered service worker's scope, then navigator.serviceWorker.controller will be set, and the page will be under the service worker's control.

I would recommend using Workbox https://developers.google.com/web/tools/workbox to manage your Service Worker functionality. Using workbox.routing module (https://developers.google.com/web/tools/workbox/modules/workbox-routing) you can specify custom rules for cashing by using specific to your app regular expressions.

Hope it will help you!