Isiah Meadows impinball at
Sun Jun 29 01:48:12 PDT 2014

I think that a possible compromise that can still make the ES6 module
system more compatible with both AMD and CommonJS modules is by this:

If there are no exports from a module, named or not, make the export
process implementation-defined. If an ES5 Node module uses module.exports,
then Node could configure the exports to be importable through the ES6
syntax. Some people use named exports, while others have even exported a
constructor via module.exports. In the browser environment, it could be
something along the lines of using the added Window properties as named
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list