Examples use es6 modules "import" in webpack config which is not supported

[aight8]

When there is a simple way with babel or so to use es6 module syntax in the webpack config it would be good when the solution will be noted in the readme. Is that a not working example or which solution did you use for that?

[catamphetamine]

I don't understand what you are saying

On Friday, July 8, 2016, Sebastian Fekete notifications@github.com wrote:

When there is a simple way with babel or so to use es6 module syntax in
the webpack config it would be good when the solution will be noted in the
readme. Is that a not working example or which solution did you use for
that?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#9, or mute
the thread
https://github.com/notifications/unsubscribe/AAdH77iCpIQV_IK7WkIIzqbmB2J-xfmNks5qTgNKgaJpZM4JHzeU
.

[aight8]

For the webpack configuration example you use ES6. But webpack config can't be ES6 since node 6 don't support ES6 import/export's only when its transcompiled with babel. Where this happens?

[catamphetamine]

Webpack config can be ES6.
First, there's webpack.config.babel.js.
http://stackoverflow.com/questions/31903692/how-to-use-es6-in-webpack-config
Second, there's always babel-register.

[aight8]

Thank you. I use now babel-node, don't knew that. Webpack is not so good documented in some parts.

[jairusd]

well babel-node is now being deprecated i have no idea where to go from here

[KresimirCosic]

I am literally just trying to get the classic import and export rules to work with the (default named) webpack.config.ts (yeah, TypeScript as well), and it's inhumanely impossible to find a good documented approach. Hilarious considering how long the system has existed.

[plutotv-aaa]

@KresimirCosic , did you find a way?