-
Notifications
You must be signed in to change notification settings - Fork 58
use new
to instantiate all buffers
#75
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
Conversation
Using Buffer without `new` will soon stop working. It will throw A deprecation warning in Node v7.
Using Buffer without new will soon stop working. It will throw A deprecation warning in Node v7. This commit modifies the tests in `test/bare.js` and `test/bare_shebang.js` to use the `Buffer.from` interface instead. It is a drop in replacement for Buffer that is supported by Node v4 / v6 and Browserify's Buffer implementation For the browserify test suite to pass on Node v7 we will need to land this commit as well as the two below PR's * browserify/browser-pack#75 * max-mapper/concat-stream#48
lgtm |
btw, this pull request fixes #76. |
Bump |
I can't see any problem with this. |
Can we please get a bugfix release for this? That would be nice. |
This doesn't fix anything. There is no clear roadmap for core. Adding |
It fixes issue #76, "annoying warning showing up in logs". |
Also don't see what the problem is with releasing a patch version in this case. Yes no logic changed, but having no deprecation warnings is a good thing. /cc @zertosh |
This shouldn't have been merged but I don't blame anyone except for node core. |
@substack we reverted in core. LMK if you would like me to submit a revert PR to browser-pack |
Using Buffer without
new
will soon stop working. It will throwA deprecation warning in Node v7.