Avoid using deprecated Buffer constructor #90
Merged
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.
This should also give performance improvements on Node.js 8+.
Use Buffer.allocUnsafe directly on Node.js >= 4.5.0
This usecase doesn't need zero-filling, as is properly filled with the parent buffer.
This behaves exactly the same as Buffer(number) on 4.x and 6.x, and slightly faster that Buffer(number) on 8.x and above, as doesn't perform zero-fill.
Older Node.js versions (<4.5.0) use the old code path.
Refs:
https://nodejs.org/api/deprecations.html#deprecations_dep0005_buffer_constructor