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

I guess it's very silly question, but may I ask why this one is a requirement?
> We need to fetch all the dependent modules, not just the single resource pointed to by the link tag

It seems to me, that in context of modules, preload is a remedy for waterfall problem, so ideal solution would be creating a flat list of all modules used in the app (as `<link>` tags). With such approach the browser could prefetch module files (I'm not sure about parsing, is it possible to do it without resolving dependencies?) and pick them from cache later, once it encounters references during recursive dependency resolution, starting from `<script type="module">` entrypoint(s). Does it make sense at all? What did I miss? It'd be parallel fetching and sequential/waterfall dependency resolution. Is the point of this feature to provide parallel DR as well?

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