Re: [w3c/ServiceWorker] Clarify dynamic-imported scripts are never installed (#1356)

F2F: There was some discussion of options:
* Match static imports.
* Make dynamic imports just like fetch(): no installation, no bouncing through FetchEvent
* Allow fetches of dynamic imports to go to the service worker's own FetchEvent to enable offline.
* Just throw on dynamic imports.

It turned out Chrome is the only browser with immediate plans to implement module service workers.

There was rough consensus that throwing on dynamic imports for now is the safe thing to do, with room to change later as we get real usage of module service workers and understand the problem more.

Todo:
* Spec that static module imports are installed
* Spec that dynamic module imports throw
* Add tests.

-- 
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/1356#issuecomment-433411852