jampy
jampy
Awesome! Thanks so much :)
Yeah, that would be important. Is that difficult to implement?
Of course. No hurry :)
Thanks, but is there a better solution to this problem? Problems: - this reloads the PWA app - my primary browser is Firefox and while this solution sends a new...
FYI, my patch needed a little fix. Here is the better version: https://gist.github.com/jampy/635ab91e60907a7fe38fb18a1c11a94d#file-sw-template-js-L631
Hi @NekR > > The only way I found to stop offline-plugin to do this is by supplying a version: () => null option, but that seems slightly hackish to...
> It's indeed redundant in your case, but I don't see how it harms you. I already said that it probably makes sense to have a way to disable __uncache,...
> In other words, to change SW file you need to unregister current one first. Ah, I see. So, using a cache-busting parameter for `sw.js` would tell the browser, that...
>When you register SW browser check registration URL for the scope, if there is already a SW and it has different URL then registration fails. In other words, to change...
Thanks for the link and the explanation - that helped a lot! :-) I completely overlooked that the "index" page is cached, too. I feared a race condition that clearly...