Harmony support

[ozanvos]

I'm trying to use the excellent livenode with a project which uses ES6 features introduced in node v11, but unfortunately UglifyJS's parser chokes when it encounters a let statement or a generator function (function *() { yield true }).

[kevyworks]

Any comment on this?

[mgol]

That would be great to have, ES6 brings a lot of important new features but minification of all of them is still needed.

[Martii]

+1

[maranomynet]

+1

[darky]

👍

[ben-eb]

+1

[kevinjalbert]

👍 just got bit by for...of.

If harmony support were enabled, we could also safely convert functions that don't use this to use the => syntax as well.

[fabiosantoscode]

+1 -- I'm writing a game for future browsers so I don't want to add the overhead of traceur to my code.

I also think converting functions to arrows when this is not used would be pretty nice.

[fabiosantoscode]

Adding harmony support on my fork, https://github.com/fabiosantoscode/UglifyJS2/tree/harmony little by little, to later pull request that back to this project.

Got arrow functions working so far (I think).

[rvanvelzen]

@fabiosantoscode Awesome! It would be super cool if you could submit separate new language features as separate pull requests. That will make reviewing them a lot easier. :)

[fabiosantoscode]

Okay, I'll restructure my commit history to do just that.

I'm writing some tests for the parser, and am thinking of doing so for the output as well, is that okay?

[rvanvelzen]

That is certainly okay! Related tasks: #337, #410.

[19h]

👍 bump.

[simonzack]

👍