Reputation: 4734
If I edit my web worker script and refresh the page, the web worker script is a cached version. I am reasonably confident it is not my webserver, because I can immediately load the latest copies of all other files, and even restarting the webserver does not fix the problem. It only loads the newest version of the web worker script if I reboot chrome, which is highly inefficient, needless to say! It doesn't fix it even if I restart chrome. Is there anything I can do to get around this?
Upvotes: 12
Views: 8263
Reputation: 650
What I found works is:
Chrome's reloading of "resources" on "shift-reload" seems to be... variable.
I hope you found this: chrome://inspect/#workers. You can terminate the worker here
Upvotes: 3
Reputation: 1
You must close all tabs which opening this page. Open only one 1 then Ctrl + Shift + R to refresh then the cache will be clear.
Upvotes: 0
Reputation: 11
Add <script src="your_worker_path"></scripts>
to your page head to force cache update.
Include code of your worker in if(typeof window == "undefined"){...}
to avoid it starting on page reload
Upvotes: 1
Reputation: 711
In your install
event, before the call to event.waitUntil
add:
if (self.skipWaiting) { self.skipWaiting(); }
Also, you can follow this development workflow:
Upvotes: 1
Reputation: 181
On my Linux Chrome I have to right click (or long click) the reload button and select "Empty Cache and Hard Reload" to get the latest version
Upvotes: 18
Reputation: 707328
Your web server determines how cachable a given web resource is and the browser attempts to respect those settings, caching resources that the web server says it is OK to cache, not caching things it says shouldn't be cached.
If you want to change that, you have these options:
Upvotes: 7