-
Notifications
You must be signed in to change notification settings - Fork 70
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
Truncated output with Node v6.0.0 #106
Comments
The issue still exists in |
I nailed it down to nodejs/node@c3cec1e. |
Fixes: #5737 Fixes: #4643 Fixes: #4291 Fixes: nodejs/node-v0.x-archive#8960 Refs: #3594 PR-URL: #5994 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
I reported it to Node.js as well in nodejs/node#6297. |
Please take a look at 1 line |
See also: https://github.com/cowboy/node-exit If In light of these workarounds I think this node ticket can be closed and no need to revert libuv 1.9.0. |
Node 6.0.0 final has been released. |
Thanks for reporting |
@alanshaw I've changed my opinion on the suitability of Uglify implemented this approach instead: https://github.com/mishoo/UglifyJS2/pull/1061/files |
The text was updated successfully, but these errors were encountered: