ES6 module support?

[dead-claudia]

Many frameworks are changing to exclusively using ES6 modules, such as Ember (already has) and Angular (will for 2.0). Currently, the only way to do a proper ES6 import is via wrapping it in double backticks like so:

``import foo from './bar'``
# do stuff with foo

This is very ugly on multiple levels. Could there be support added for ES6 module syntax?

One potential issue may be reserving/replacing the import operator, but getting people to shift to the current equivalent to << (or import all to <<<) could be a start.

(Note: apparently this even has some traction in making it into CoffeeScript, whose implementors have historically put web-compat as first priority)

[vendethiel]

(Note: apparently this even has some traction in making it into CoffeeScript, whose implementors have historically put web-compat as first priority)

I'm a coffee "maintainer" as well, and web compat is the reason we consider adding es6 features. But you'll have to point me to where the "traction" is ;-).

[dead-claudia]

I'm a coffee "maintainer" as well, and web compat is the reason we consider adding es6 features. But you'll have to point me to where the "traction" is ;-).

Okay...or at least a very noisy bug filled with people pleading for some sort of support (more so towards the bottom). Also, this bug kinda documents some of the patterns going on.

It was definitely the case (in a more limited form) with generators.

I must have inferred incorrectly.

[vendethiel]

Generators "happened" because somebody (actually, 3 people) opened PRs. That's what works best

[vendethiel]

I'll reopen this, because I think we want this. We just need somebody who actually uses them to get some time for them :-).

[dead-claudia]

Good point. I was just closing a seemingly stale issue (that I don't have the time to devote to).

[gkz]

Continue discussion at #705