Re: [whatwg/fetch] preload, destinations, and module scripts (#486)

As far as I can tell from a quick glance at the spec it sounds like the distinction between `worker` and `script` is needed to handle subresource boundaries, while`importScripts` in workers are still loaded as `script`. Could the same distinction not apply to modules - separating moduleworker, modulesharedworker and moduleserviceworker as simply the top-level goals, while their dependencies would still run through `module`? If so, `moduleworker`, `modulesharedworker` and `moduleserviceworker` may be less important from a preloading perspective, allowing a `module` implementation to land as the primary priority first. Personally I'd like to see web assembly and binary ast header-detected under the same `module` destination name as well, but am weary of taking this too off-topic.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/486#issuecomment-324727785