James Burke jrburke at
Fri Aug 21 14:33:12 UTC 2015

On Tue, Aug 18, 2015 at 11:36 AM, Dave Herman <dherman at> wrote:

>From a loader/tool perspective, it seems like working out more of the
Stage 1 items before many of the Stage 0 items will lead to higher
leverage payoffs: the dynamic loading and module meta help existing
transpiling efforts, better inform userland module concatenation

In the spirit of the extensible web, defining these lower level APIs
and more of the loader would make it possible to use custom elements
to help prototype a <module> tag. The custom element mechanism can be
used in a similar way to how JS transpilers are used for the existing
module syntax.

If the Stage 0 normalization is about normalizing IDs to URLs as the
internal normalized storage IDs, I suggest reaching out to talk with
more people in the AMD loader community about the reasons behind it,
how it sits with AMD loader plugin IDs, seeing IDs more like scoped,
nested property identifiers, and module concatenation.


More information about the es-discuss mailing list