In order for the update to take effect you need to:
- Change some code inside the main service worker (if you only change code inside a script imported with importScripts the browser will not detect the change)
- Visit a page of the website (that activates the service worker or calls serviceWorker.register) – sometimes you also need to refresh that page
- Now the new service worker is installed, but it can’t be activated until you terminate the previous service worker: close and reopen the browser
If a user doesn’t visit your website, but the service worker is activated by the push messages, the browser will try to fetch a new version of the service worker automatically after 24 hours (this behavior is described by Google, but probably is not implemented in all browsers yet).
Note that scripts imported with importScripts are cached by the browser and even if you have updated the main service worker they may not get updated. In order to force the update of the imported scripts add a query string to the imported script path.
For example, if you have the following line inside your service worker:
You can force the update of the service worker and its dependency by adding an arbitrary query string (e.g. v2, v3, v4… the current timestamp, or anything else – the query string
?foobar would have the same effect):
If you want to make sure that the the service worker code that runs in your browser is updated you can use the browser developer tools.
Note that this behavior will be fixed in the future versions of the browsers and you can expect easier updates. However, on April 2017, you still need to use this hack.
2 thoughts on “Update the service worker and the scripts imported with importScripts”