Fresher service workers, by default | Blog | Chrome for Developers

tl;dr Starting in Chrome 68, HTTP requests that check for updates to the service worker script will no longer be fulfilled by the HTTP cache by default. This works around a common developer pain point, in which setting an inadvertent Cache-Control header on your service worker script could lead to delayed updates. If you've already opted-out of HTTP caching for your /service-worker.js script by se

[efcl]

Chrome 68まではService Workerの登録スクリプトがHTTPCache-Controlなどをみていたが、今後は`updateViaCache`でこの動作を制御できるように。 `imports`がデフォルトの動作となる