import / export

[reggi]

One of the big things for me is support for import / export, which is in es2015, why isn't this in your list?

[williamkapke]

Yeah, it is ES2015 and should be part of the list. Because this project uses Kangax's tests it will only display categories they include. Currently, they do not have a test for it. See: compat-table#316

Node will be using a special file extension to load modules- so that requires any tests to be save to their own files- which will require some reworking of how my scripts run.

The answer for Node (currently) is: Not implemented.

[ericgrosse]

What's the point of using ES6 in a node environment if such a key feature is missing?

I did find a polyfill for it here, but it would be nice to run a node environment that doesn't require babel in some way, shape or form.

[ljharb]

@ericgrosse the loader spec isn't finished, so ES modules don't actually exist yet. import/export don't actually do anything per the ES6 spec.

[ghost]

I'm a little confused. This compat table currently lists ES2015 Support for Node 6.10 and above as 99%. Without Modules support wouldn't that make the metrics inaccurate?

[ljharb]

No, because Modules do not yet exist.

ES6 only contains Module parsing goal semantics (which an engine does not have to implement if they don't provide a way to get there). That's only one piece of "ES Modules".

[ghost]

I see. Thanks for clarifying. I believe what I'm looking for is Node support for ES2016, then.

[ljharb]

ES2016 over ES2015 only adds ** and Array.prototype.includes. ES2017 adds async function, and a number of new API methods. ES Modules, as a whole concept, won't ever be in the ES language spec - just the building blocks for them that ES2015 ships.

[FossPrime]

as of 8.7 it's behind a flag. It's still behind a flag on 9.0

[jaggli]

Can we simply add it to the list for good measures? It's also in the docs