Fix usage of deprecated Buffer API #1647
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
|
@substack any chance of merging this harmless PR? Those Node 7 warnings are pretty annoying. |
|
This patch updates tests. Why? This patch ONLY updates tests, which I also don't understand. |
|
I don't like this. |
ghost
closed this
Author
|
You don't like this because it updates tests?
"Only tests were affected." #1647 (comment) |
4 tasks
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #1616. Only tests were affected.
Once Node.js 0.12 reaches EOL (January 1 2017), or whenever you feel comfortable with dropping 0.12 support, you can safely remove the "safe-buffer" dependency and the
requires.