Skip to content

Avoid using deprecated Buffer constructor#53

Closed
ChALkeR wants to merge 1 commit intospdy-http2:masterfrom
ChALkeR:patch-1
Closed

Avoid using deprecated Buffer constructor#53
ChALkeR wants to merge 1 commit intospdy-http2:masterfrom
ChALkeR:patch-1

Conversation

@ChALkeR
Copy link
Copy Markdown

@ChALkeR ChALkeR commented Mar 2, 2018

safe-buffer is already used and provides Buffer.alloc polyfill, so just use Buffer.alloc directly to avoid hitting deprecated API.

Refs:
https://nodejs.org/api/deprecations.html#deprecations_dep0005_buffer_constructor

Tracking: nodejs/node#19079

safe-buffer is already used and provides Buffer.alloc polyfill, so
just use Buffer.alloc directly to avoid hitting deprecated API.

Refs:
https://nodejs.org/api/deprecations.html#deprecations_dep0005_buffer_constructor
@jacobheun
Copy link
Copy Markdown
Contributor

I added this into the latest fixes for node LTS support #61 and it is available in spdy-transport@3.0.0

@jacobheun jacobheun closed this Nov 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants