Ignite
Ignite copied to clipboard
switch to uglifyjs alternative
Which alternative? What is the driving force behind wanting to switch?
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 [email protected] 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 https://github.com/intuit/Ignite/issues/82#issuecomment-447516098, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIyBJ2X7dobZme41YtPiGJy0Jl17nkbks5u5D69gaJpZM4ZSv5R .
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?
The mangle: false
option in uglify might also resolve the issue
webpack is switching to terser so that why it was my go to https://github.com/webpack/webpack/issues/7923
seems its been merged https://github.com/webpack/webpack/pull/8392
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.
As in "Reason for switching?" is a terser way of saying "What is the driving force behind wanting to switch?"
Hi, I'd like to pick up this issue! Lmk if there are any specific guidelines to be aware of for contributions :D
No specific guidelines! go for it