[refactor] Use Buffer.allocUnsafe instead of new Buffer#104
Merged
darrachequesne merged 1 commit intosocketio:developfrom Oct 31, 2018
Merged
Conversation
828bd39 to
4270da5
Compare
darrachequesne
added a commit
that referenced
this pull request
Nov 1, 2018
Breaking change: drop support for Node.js 4 (since Buffer.allocUnsafe was added in v5.10.0) Reference: https://nodejs.org/docs/latest/api/buffer.html#buffer_class_method_buffer_allocunsafe_size
darrachequesne
added a commit
that referenced
this pull request
Mar 19, 2019
Breaking change: drop support for Node.js 4 (since Buffer.allocUnsafe was added in v5.10.0) Reference: https://nodejs.org/docs/latest/api/buffer.html#buffer_class_method_buffer_allocunsafe_size
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.