ES modules: syntax import vs preprocessing cs plugins

Allen Wirfs-Brock allen at wirfs-brock.com
Tue Jul 3 16:19:50 PDT 2012


On Jul 3, 2012, at 3:36 PM, Sam Tobin-Hochstadt wrote:

>> ...
> 
> [problems snipped]
> 
> There are two issues here.  One is what code evaluated in nested
> loaders looks like.  That's entirely up to the loader, but it
> certainly can use `import` and `export` and all of the other features
> of the module system.  Those references are resolved by the loader
> being used.
> 
> The second question is how we specify a particular loader to use.
> This is easy to do in JS code: `myLoader.load(url, callback)`.  If we
> want convenient syntax for using this in a particular environment,
> then that would require an extension to the environment, such as an
> HTML declaration to use a particular loader for the rest of the page,
> or for a particular script tag.  This is certainly doable, but
> requires coordination outside of TC39.

Sam, 
Isn't it also the case that the full characteristics of the default module loader used by browsers still remain to be specified?  This might be somewhat out of scope for TC39 put practically speaking it's something we will need (and want) to be involved with.

Allen






> -- 
> sam th
> samth at ccs.neu.edu
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
> 



More information about the es-discuss mailing list