ES6 support

[sokra]

https://github.com/webpack/webpack/tree/harmony/examples/harmony#examplejs

[gaearon]

I think I saw NPM 2.0 erroring on this kind of thing since it's not allowed to reference -dev versions in new semver. Not sure though.

[sokra]

hmm... We need to redesign this to get all advantages of ES6 modules. Instead of tracking which module is requested, we need to track which export is requested. That way we can optimize away unused imports/exports and remove modules that only reexport (which is a common pattern for package entries, i. e. react-router)

[jhnns]

Instead of tracking which module is requested, we need to track which export is requested.

👍

[gaearon]

This would be rad.

[sebmck]

I'd recommend using acorn over esprima. It has far better ES6 support, and is much faster.

[zxcabs]

What about System? for example: https://github.com/systemjs/systemjs

[jhnns]

System has nothing to do with ES6 support as far as I read it out.

[zxcabs]

System is a part of ES6

Look par.8 http://www.2ality.com/2014/09/es6-modules-final.html

[sokra]

System.import can act as Code Splitting point.

System.set System.define System.module propably won't be supported...

[jhnns]

@zxcabs Ah, you were talking about the ES6 System. I've understood it as answer on @sebmck 's post and thought you were suggesting that systemjs should somehow be used by webpack.

[simonzack]

Agree with @sebmck. esprima support will likely take some time. Acorn also uses the mozilla parser API..

[sokra]

closed in favor of #857