-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(node): rollback changes of Buffer.from to new Buffer() #3986
Conversation
…own travis to 4.3 min node v
@@ -65,7 +65,7 @@ | |||
"worker-loader": "~0.7.0" | |||
}, | |||
"engines": { | |||
"node": ">=4.7.0 <5.0.0 || >=5.10" | |||
"node": ">=4.3.0 <5.0.0 || >=5.10" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change the line to just "node": ">=4.3.0"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still don't want to support node 5 though?
@@ -408,6 +408,10 @@ buffer-shims@^1.0.0: | |||
version "1.0.0" | |||
resolved "https://registry.yarnpkg.com/buffer-shims/-/buffer-shims-1.0.0.tgz#9978ce317388c649ad8793028c3477ef044a8b51" | |||
|
|||
buffer-v6-polyfill@^1.0.3: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is buffer-v6-polyfill
necessary if you change Buffer.from
to new Buffer
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will get de committed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't been to check-in in lock for
Thanks |
What kind of change does this PR introduce?
Bugfix
Did you add tests for your changes?
N/A
If relevant, link to documentation update:
N/A
Summary
Because AWS Lambda (see #3984) is only supporting node 4.3 😦 as their max version, this PR rollsback use of
Buffer.from
in favor of the cross version supportednew Buffer
. It is deprecated for the future, but currently, warnings nor errors will emit from use ofnew Buffer
even in Node 7@latest. To ensure that this is testing accurately, I've bumped our CI version for node down to 4.3 on travis as well and updated the engine field in ourpackage.json
Does this PR introduce a breaking change?
No
Other information
Fixed #3984