Uglifyjs: What is backwards incompatible in 3.0?

[curiousdannii]

You've just pushed out a new semver major release to thousands of people with no indication of what is new or backwards incompatible. There's no changelog, no descriptions in the releases page, no blog post at http://lisperator.net, all there is is the list of commits, none of which seem to be marked as semver major that I can see.

Unless I've missed something, this is a very unhelpful release process. Changelogs are very important for downstream users.

[alexlamsl]

Thank you for your insightful comments.

[curiousdannii]

For anyone who's wondering, here are the 34 commits that differ between 2.8.22 and 3.0.0 (not the 313 which Greenkeeper tells me (I guess for me it is comparing against a much older version than 2.8.22)).

[curiousdannii]

@alexlamsl Wait, you can't just close this! You really should tell us what the backwards incompatible changes are!

[SenHeng]

This PR seems to contain a list of changes to the CLI/API at least.

https://github.com/mishoo/UglifyJS2/pull/1811

Then there's also this bit about dropping support for AngularJS.

https://github.com/mishoo/UglifyJS2/pull/1812

[gotofritz]

@alexlamsl - what an unhelpful response. @curiousdannii was perhaps a bit curt, but asking for a changelog seems a perfectly reasonable request

[julianlam]

I see @alexlamsl has been active today. I'd like to hear from him to discover why this issue was closed prematurely. Perhaps there is a changelog already? A link to such a page would not go amiss here.

To @SenHeng's reply -- latest UglifyJS is broken for us, yet we do not use the CLI interface nor is our code using Angular.

[SenHeng]

A quick glance at the contributors' graph shows that @alexlamsl has done the bulk of the work updating this library for the past year. While it would be nice to have some updates, he is still just one man. The simple solution is to stick with v2 for the time being.