Question
Hi,
I want to know if having multiple runtime installations for the Service worker could cause any issue. Some backstory , I'm working on an app , which uses a library. This library uses the offline-plugin to cache the web-pack assets and therefore it has a offline-plugin runtime installation of it's own. The app that i'm working on uses this library at only certain scenarios (only when the user visits a certain URL.). What's happening is that , the SW is set to cache some parts of the app that i'm working on plus whatever the library needs.
Since , the library comes into picture only when someone access a particular URL , the Service worker is only installed when the user visits that URL. To make sure that Service Worker is installed as soon as the user opens the app , i added an extra runtime installation. Would it cause any troubles ?
Question
Hi,
I want to know if having multiple runtime installations for the Service worker could cause any issue. Some backstory , I'm working on an app , which uses a library. This library uses the offline-plugin to cache the web-pack assets and therefore it has a offline-plugin runtime installation of it's own. The app that i'm working on uses this library at only certain scenarios (only when the user visits a certain URL.). What's happening is that , the SW is set to cache some parts of the app that i'm working on plus whatever the library needs.
Since , the library comes into picture only when someone access a particular URL , the Service worker is only installed when the user visits that URL. To make sure that Service Worker is installed as soon as the user opens the app , i added an extra runtime installation. Would it cause any troubles ?