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

+1.  This seems like a prime example of perfect as the enemy of good.  Now that browser support for modules is actually rolling out, it's becoming more important to be able to actually load them efficiently.  Closure Library is currently working on integrating modules into our debug loader (in which case we already have a flat list of all recursive dependencies), but with zero support for preloading modules, there seems to be no way to interleave non-module execution between two modules without waiting for a bunch of serial fetches.  Given that `<link rel=preload as=script>` works fine for non-recursive loading of scripts, making it also work with the same non-recursive semantics for modules seems like a reasonable option.  If we want to later hammer out and add a recursive version, that's fine, but please don't block something that's (seemingly) straightforward and actually very useful on a unicorn that may never materialize.

-- 
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-324500389