Uglifyjs: Issue Overload!

[bnjmnt4n]

Currently this repository is filled with loads of issues, so I’m suggesting that one of the maintainers do some cleanup. To get you started, I’ve browsed through some of the latest issues and made a list of duplicates and stuff which seem like they should be merged.

• Issues #332 and #446 are duplicates of #88, and should be tagged as such and closed.
• Issue #467 is a duplicate of #448.
• Issues #421, #464, and #455 seem like they should be merged.

I will try to review other issues and will add more updates here. Keep up the good work maintaining UglifyJS! :)

[bnjmnt4n]

More updates:

• Issue #370 should be merged, which would also fix #369.
• Issue #339 is a duplicate of #448 requesting for ES6 support.
• Issue #271 should be merged.
• Issue #342 can be closed.
• Issue #416 has wrong information and can be closed.
• Issue #288 should be closed as a wontfix.
• Issue #238 should be closed.
• Issue #249 is not actually related to this repository.
• The uglify-js2 package on npm should be updated, allowing #290 to be closed.

[bnjmnt4n]

258 can be closed since it’s already been done.

[bnjmnt4n]

Issue #180 is yet another duplicate of #88.

[bnjmnt4n]

Regarding my earlier comment about #290, didn’t realise that the uglify-js2 package was deprecated, I suggest you just close #39, #89, and #290 instead. Eventually it would be great to just unpublish that package.

[mishoo]

Thanks for the breakdown! I know I'm lagging behind here and your summary will be helpful. Hope I can go through it in the next few days.

[bnjmnt4n]

Do you need some help? I will be free next week after exams :smile_cat:

[bfricka]

:+1: Just bumping this since it's a genuinely helpful one.

[emgeee]

I'll give it another bump :+1:

[rvanvelzen]

As of today I'll be trying to get the open issue list to a near-zero number. Your list has been valuable. :+1:

It's a herculean task, so any feedback is greatly appreciated.

[avdg]

@d10 Do you have time to update the status of these issues?

[codemakerlive]

Possibly these 2 merge?:

Is it possible to preserve inline sourcemaps? #780
allow inlined source maps in compiled JS #520

[avdg]

I prefer to close this issue in preference to get a new issue with a more updated list of things to do. I prefer not to dwell in bugs that might already have been fixed.