This repository has been archived by the owner on Aug 19, 2020. It is now read-only.
Avoid using deprecated Buffer API #21
Merged
Conversation
This file contains 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
Buffer.alloc creates a zero-filled buffer, supported since Node.js 4.5.0 That is well below the current Node.js version requirement (>=8.9.0) and async usage. Refs: https://nodejs.org/api/deprecations.html#deprecations_dep0005_buffer_constructor
|
Tracking: nodejs/node#19079 |
|
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Buffer.alloccreates a zero-filled buffer, supported since Node.js 4.5.0That is well below the current Node.js version requirement (>=8.9.0) and async usage.
Refs:
https://nodejs.org/api/deprecations.html#deprecations_dep0005_buffer_constructor