I see there are now two load functions for the ES6 module loader -
'Loader.import' and 'Loader.load'. Loader.import seems to apply the full
normalization process, while Loader.load takes a url directly. This sounds
like a good feature to me.

>From the code comments in the reference loader at
https://github.com/jorendorff/js-loaders/blob/master/loaders.js#L142 it
seems that any 'import' statements in code loaded with 'Loader.load' will
still be respected.

I was wondering if 'export' statements would similarly cause a module to be
returned by the 'Loader.load', and if so, why is the 'type' metadata in the
translate and link hooks necessary? Surely the lack of a 'normalized'
property in the metadata would implicitly indicate this anyway?

Thanks,

Guy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130621/32da610e/attachment.html>

I see there are now two load functions for the ES6 module loader -
`Loader.import` and `Loader.load`. `Loader.import` seems to apply the full
normalization process, while `Loader.load` takes a url directly. This sounds
like a good feature to me.

From the code comments in the reference loader at
https://github.com/jorendorff/js-loaders/blob/master/loaders.js#L142 it
seems that any `import` statements in code loaded with `Loader.load` will
still be respected.

I was wondering if `export` statements would similarly cause a module to be
returned by the `Loader.load`, and if so, why is the `type` metadata in the
translate and link hooks necessary? Surely the lack of a `normalized`
property in the metadata would implicitly indicate this anyway?