switch to uglifyjs alternative

[hipstersmoothie]

No description provided.

[bowbahdoe]

Which alternative? What is the driving force behind wanting to switch?

[hipstersmoothie]

Terser. Reason for switching? I was using ignite and uglify was breaking my prod build

…

On Fri, Dec 14, 2018 at 4:13 PM Ethan McCue ***@***.***> wrote: Which alternative? What is the driving force behind wanting to switch? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#82 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABIyBJ2X7dobZme41YtPiGJy0Jl17nkbks5u5D69gaJpZM4ZSv5R> .

[bowbahdoe]

Off the top of my head the only other source aware minifier I can think of is the Google Closure Compiler. That would definitely break more than uglify, so it isn't a good option. Maybe switching to just whitespace only optimizations would do the trick?

[bowbahdoe]

The mangle: false option in uglify might also resolve the issue

[hipstersmoothie]

webpack is switching to terser so that why it was my go to webpack/webpack#7923

[hipstersmoothie]

seems its been merged webpack/webpack#8392

[bowbahdoe]

Oh I thought you said Terser as in you were going to say the next sentence in a Terser way. I did not know that was a thing.

[bowbahdoe]

As in "Reason for switching?" is a terser way of saying "What is the driving force behind wanting to switch?"

[alinewm]

Hi, I'd like to pick up this issue! Lmk if there are any specific guidelines to be aware of for contributions :D

[hipstersmoothie]

No specific guidelines! go for it