-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update uglify #453
Update uglify #453
Conversation
@XhmikosR that warning is new but harmless - it merely states the fact that the despite specifying I guess a test in this project has set that specifically. |
I'll see how to work around this then. Are there any breaking changes though? |
e9eac24
to
ebdda8c
Compare
Not sure if these counts as well, but |
OK, thanks. Those shouldn't affect us. |
@XhmikosR please consider applying the one-liner from mishoo/UglifyJS#1516 (comment) |
@alexlamsl; you mean in this branch? Note that I have no idea why they say there they get 2.8.0 since we use a tilde for uglify so it shouldn't get that. |
@XhmikosR I mumbled about that in mishoo/UglifyJS#1519 (comment) as well. Anyway, this new method is introduced back in |
@alexlamsl: so I apply that one line patch and I get different output. Is that normal? I pushed the patches in this branch for you to have a quick look. |
@XhmikosR the minified Thanks! |
I'm gonna merge this and release the new version in a few hours. |
2.8.3 will be released shortly: |
@kzc: although it shouldn't matter due to us using tilde for uglify version, I can wait for 2.8.3, rebase and then release the new version. |
@XhmikosR True, but that |
|
/CC @ @alexlamsl: are there any breaking changes in 2.8.0 we should take care of? So far I see Windows builds fail due to
WARN: Output exceeds 40 characters
.