Harmony support

[ozanmakes]

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.

[ghost]

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]

👍

[RamIdeas]

👍

[lewispham]

👍

[avdg]

I hope everyone knows how to find technical information about ecmascript 6 / ecmascript 2015

Some examples:

• Candidate specs: http://wiki.ecmascript.org/doku.php?id=harmony:specification_drafts
• Es discuss: https://esdiscuss.org/

Note: understanding the structure of the spec, instead of reading it may be more important long term, so its easy to find information about specific items of the spec.

Good luck

[niemyjski]

+1

[f0rmat1k]

👍

[mgol]

@hamosapience you made a typo in the message; it says "depreceted" instead of "deprecated". Also, it directs people to uglify-js which is the stable version that doesn't understand ES6. It'd be better to mention uglify-es.

[Martii]

@alexlamsl

Re current README.md currently states npm install uglify-js -g which doesn't seem completely synonymous with:

harmony branch will now be published on https://www.npmjs.com/package/uglify-es

So which npmjs.com source is correct... https://www.npmjs.com/package/uglify-es or https://www.npmjs.com/package/uglify-js ?? e.g. they both point to uglify-js for npm installation... which can be confusing to newer users.

Thanks for the look.

[graingert]

@Martii both are correct, uglify-es is the Harmony branch, and uglify-js is the master branch

[Martii]

@graingert
So the https://www.npmjs.com/package/uglify-es page at npmjs.com is reading the master here on GH then... since it says to install with npm install uglify-js -g e.g. it should say npm install uglify-es -g.

---

Should be...

• ES5 → https://www.npmjs.com/package/uglify-js → https://github.com/mishoo/UglifyJS2/blob/master/README.md
• ES6+ (ES2015+) → https://www.npmjs.com/package/uglify-es → https://github.com/mishoo/UglifyJS2/blob/harmony/README.md

... but is currently ...

• ES5 → https://www.npmjs.com/package/uglify-js → https://github.com/mishoo/UglifyJS2/blob/master/README.md
• ES6+ (ES2015+) → https://www.npmjs.com/package/uglify-es → https://github.com/mishoo/UglifyJS2/blob/master/README.md

Cc: @isaacs ... is there a way to have npmjs.com read the harmony branch README.md correctly? Thanks for the visit in advance.

[alexlamsl]

Documentation for uglify-es has been updated for 3.0.3, which is yet to be published on npm pending green light from Travis.

[sbrl]

Suggestion: Set up Gitter for general discussion if you haven't already, and then put a link in the README to it.

[Polve]

I'm unable to understand how to correctly integrate uglify-es with the usual ember build pipeline: a few weeks ago I just had to add the dependency "uglify-js": "git://github.com/mishoo/UglifyJS2#harmony" but this not work any more.

I tried removing ember-cli-uglify and depending instead by ember-cli-uglify-es but this not seems to work too.

Can anyone please give me an hint?

[avdg]

Note that the api has been changed on harmony because of the breaking changes. This is done as preparation for uglifyJS v3.

[fritx]

@Polve if you're using webpack@1 and mishoo/UglifyJS2#harmony and have met the uglify-es problem, then you must be in the same trouble as I was.

You could try my fork of webpack and re-install, it would help.
https://github.com/fritx/webpack/tree/1.x-harmony
as mentioned here #448 (comment)

npm i -D "git+https://github.com/fritx/webpack.git#1.x-harmony"

This fork is including uglify-js < 3, and can work well.

[Polve]

I'm not using webpack, and I'm still stuck, unable to create a production build :-(

[kzc]

I'm not a webpack user, but you could try:

https://github.com/noBlubb/uglify-es-webpack-plugin

[tetreault]

In comparison Sputnik 1 was pretty much designed in 3 years and launched if Wikipedia isn't lying to me.

[isaacs]

Hey. npm doesn't read the readme.md file from GitHub. It reads the local file at publish time. To change it, publish a new version.

[alexlamsl]

@isaacs thanks for the confirmation. I believe this has been taken care of in #448 (comment)

[Martii]

npm doesn't read the readme.md file from GitHub. It reads the local file at publish time.

That explains a bit. Thanks.

[bahmutskyi]

Does someone know how to integrate uglify-es in grunt project?

[ghost]

Sounds like a great question for stack overflow

[alexlamsl]

@BagMA use the harmony branch of grunt-contrib-uglify:
https://github.com/gruntjs/grunt-contrib-uglify/tree/harmony

[kzc]

use the harmony branch of grunt-contrib-uglify:
https://github.com/gruntjs/grunt-contrib-uglify/tree/harmony

Is there an official grunt-contrib-uglify npm package for uglify-es?

[ghost]

RTFM

[kzc]

@alexlamsl Since uglify-es has been released as the npm package for the uglify harmony branch, can this thread be closed to comments?

[alexlamsl]

@kzc sure thing 👍