Will start digging into https://people.mozilla.org/~jorendorff/es6-draft.html#sec-runtime-semantics-loader-state.

It's nice and dense. Any help/guidance would be appreciated :)

We should deal with this sooner rather than later because I'm about to add my own dependency system to HTML for <script needs> and so on. I _really_ don't want us to end up with three separate systems...

I think what might make the most sense is for HTML to define the dependency fetching system, including things like delaying loads until something needs the dependency, precaching, deferring, etc, whether loads should block other scripts from executing, whether to early-execute or late-execute when there's a dependency chain, etc, and for the JS module system to just have hooks that HTML bootstraps into this system. (We're going to need to have hooks anyway for actually fetching things over HTTP.)

In the case of modules in particular, having all this would allow us to hook modules into the dependency tree before actually fetching any files, so that they could be lazily loaded without requiring multiple round-trips to fetch all the dependencies once they _are_ needed.

Reassigning to dglazkov since he's organising a summit or something for this.

Moved to https://github.com/w3c/webcomponents/issues/188