-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bad output generated by 3.4.9. #3245
Comments
With the following lines appended to the input in the top post: var arr = [];
var size = utf8_write("¯\\_(ツ)_/¯", arr, 0);
console.log(size, JSON.stringify(arr)); Expected:
Actual:
Workaround:
|
How about remove this version from NPM ? |
Is this the same bug? or should I open a new issue? A problem with lodash slice when called with no length argument to clone an array
becomes
Now, if e = undefined, then the assignment is moved to inside the parameters, but after the e param e.g. uglify assumes
answers
but it doesn't - it answers
|
It looks like this error does not affect the |
mishoo/UglifyJS#3245 documents a bug which occurs when using compression. There does not appear to be any way to disable this particular path through the uglifier.
# Release Notes Tech task: Revert Uglifier to 4.1.18, due to bug in Uglify 3.4.9 # Additional Context mishoo/UglifyJS#3245 documents a bug which occurs when using compression. There does not appear to be any way to disable this particular path through the uglifier.
# Release Notes Tech task: Revert Uglifier to 4.1.18, due to bug in Uglify 3.4.9 # Additional Context mishoo/UglifyJS#3245 documents a bug which occurs when using compression. There does not appear to be any way to disable this particular path through the uglifier.
Edit: See #3278 (comment) and following. |
@mishoo Are you still maintaining this project? Seems this version causing problems all the time since your last release. |
# Release Notes Tech task: Revert Uglifier to 4.1.18, due to bug in Uglify 3.4.9 # Additional Context mishoo/UglifyJS#3245 documents a bug which occurs when using compression. There does not appear to be any way to disable this particular path through the uglifier.
# Release Notes Tech task: Revert Uglifier to 4.1.18, due to bug in Uglify 3.4.9 # Additional Context mishoo/UglifyJS#3245 documents a bug which occurs when using compression. There does not appear to be any way to disable this particular path through the uglifier.
fixes mishoo#3245 fixes mishoo#3257 fixes mishoo#3260 fixes mishoo#3269 fixes mishoo#3271 fixes mishoo#3278 fixes mishoo#3309 fixes mishoo#3319 fixes mishoo#3321
Bug report
Uglify version (
3.4.9
)JavaScript input (The source is from protobufjs. )
JavaScript output
The first
e++
is wrong.The output generated by 3.4.8 is fine.
The text was updated successfully, but these errors were encountered: