[w3c/ServiceWorker] Old React.JS App with sw.js never ditches and switches to new Svelte.JS App with service-worker.js (#1578)

This is more of a usage question rather than an issue.

How would I force any browsers who have loaded an old project written in React.JS with a sw.js to reload a brand new service-worker.js instead, and it's corresponding app, and files, etc... 

My app appears to be locked into the old sw.js, and won't load the new service-worker.js

I don't want to have every client to have to manually perform an administrative stop/unregister/reload under Application or any other hard reset of SW procedure... because that could be thousands of users.

Not sure how to go about this... I have placed a sw.js inside the new project alongside service-worker.js and it's sole purpose is to find and destroy any service workers currently found in the browser pertaining to the endpoint. But it doesn't register a new service-worker.js I don't think. There's no way for me to test this properly because the old app hosted on S3 and was Client Side, and the new app is hosted as a Lambda Function, and is Server Side.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1578