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
Yarn 1.6.0 prints deprecation warning using node 10 rc #5704
Labels
Comments
Duplicate of #5477 ? |
As a workaround for now, I've created a
|
rhysd
added a commit
to neovim/node-client
that referenced
this issue
May 18, 2018
rhysd
added a commit
to neovim/node-client
that referenced
this issue
May 18, 2018
…s fixed From Node v10, some deprecated `Buffer` APIs were deleted and it breaks Yarn v1.6.0. Until new Yarn version is published, we need to continue to use Node v9 to avoid this problem. Yarn's fix is ongoing at this PR: yarnpkg/yarn#5704
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Bug, I suppose
What is the current behavior?
Comes from
tar-stream
: https://github.com/mafintosh/tar-stream/blob/d38b9661d28923e7c31b47c1c012ff8ffb46ecb5/pack.js#L14See mafintosh/tar-stream#79
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
No warning, although I'm not sure if there's anything you can do in yarn (beyond changing out the dep)
Please mention your node.js, yarn and operating system version.
node 10.0.0-rc.0, yarn 1.6.0, macOS
The text was updated successfully, but these errors were encountered: