Do Anonymous Exports Solve the Backwards Compatibility Problem?

Domenic Denicola domenic at domenicdenicola.com
Thu Dec 20 17:32:10 PST 2012


On Dec 20, 2012, at 19:02, "David Herman" <dherman at mozilla.com> wrote:

> On Dec 20, 2012, at 1:29 PM, Brendan Eich <brendan at mozilla.com> wrote:
> 
>> So the particular approach -- in particular -- that you are questioning is adding export = to ES6 modules. I agree it is ad-hoc. It also seems likely to confuse, compared to the self-hosted NPM precedent. It's one of those almost-but-not-quite-the-same things where the differences seem likely (to me at any rate) to bite back.
> 
> I think the complaint about the syntactic similarity and semantic difference between `export = { ... }` and `export { ... }` is a very strong point, even though I don't believe it's Andreas's primary objection. ;-)

I'd be a fan of coloring the bikeshed `export only { … }`



More information about the es-discuss mailing list