readme suggestion about terser HOT 7 CLOSED

README updated: 3ef6879

Thanks.

from terser.

@olsonpm No worries. I just wanted to keep the description brief and critiquing a PR would have taken more time than just making the doc change.

from terser.

duplicate of #53

from terser.

@kzc this is not a duplicate of #53. The entire point is to make this information along with a concise recommendation readily available at the top of the readme.

There will be an increasing number of devs who end up here in the coming months, and it's a really poor experience right now to have to dig through issues like #2 and #53 to figure out what will be on everyone's mind.

Please add a more concise version of #53 to the readme.

from terser.

Nice username reporter... anyhow @kzc it would be agreeable to have what you said in a mission statement in a wiki page, with perhaps a singular reference link somewhere else... although I've already investigated this myself for our project and we're anxious and willing. :)

from terser.

The readme states

terser is API/CLI compatible with uglify-es and uglify-js@3.

But per kzc's comment that doesn't seem to be the intent of this repo. Would it make sense to remove that and have something more like

What is terser?

Forked from uglify-es, terser is a JavaScript parser, mangler/compressor and beautifier toolkit for ES6+.

Why choose terser?

uglify-es is no longer maintained and uglifyjs does not support ES6+. Additionally, this project is intended as a superset of uglifyjs (can minify any code that uglifyjs can) as we attempt to port both fixes and features into terser.

Personally I find "why" at the top of readmes to be very helpful. Without it I end up digging a while to understand whether I need a tool.

from terser.

Sorry I would have created a PR - I just wasn't sure you guys would be for it.

from terser.