Skip to content
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

Does not support NodeJs 10. #5727

Closed
p3x-robot opened this issue Apr 25, 2018 · 19 comments
Closed

Does not support NodeJs 10. #5727

p3x-robot opened this issue Apr 25, 2018 · 19 comments
Assignees
Labels

Comments

@p3x-robot
Copy link

Does not support NodeJs 10.

@Almo7aya
Copy link

I've the same issue please fix 😢,
I don't want to downgrade my nodejs version.

@p3x-robot
Copy link
Author

yarn install --ignore-engines

@Oceanswave
Copy link

lerna.json:

  "npmClient": "yarn",
  "npmClientArgs": ["--ignore-engines"],

@ksmithut
Copy link

ksmithut commented Apr 25, 2018

.yarnrc

--ignore-engines true

@p3x-robot
Copy link
Author

@Oceanswave what is lerna.json ? 😀

@a9udn9u
Copy link

a9udn9u commented Apr 27, 2018

I'm not able to add any packages after upgraded to node 10.

$ yarn --verbose add uuid
yarn add v1.6.0
(node:5003) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
verbose 0.261 Checking for configuration file "/tmp/app/.npmrc".
verbose 0.261 Checking for configuration file "/Users/[user]/.npmrc".
verbose 0.261 Checking for configuration file "/usr/local/etc/npmrc".
verbose 0.261 Checking for configuration file "/tmp/app/.npmrc".
verbose 0.262 Checking for configuration file "/tmp/.npmrc".
verbose 0.263 Checking for configuration file "/tmp/app/.yarnrc".
verbose 0.263 Checking for configuration file "/Users/[user]/.yarnrc".
verbose 0.263 Found configuration file "/Users/[user]/.yarnrc".
verbose 0.263 Checking for configuration file "/usr/local/etc/yarnrc".
verbose 0.263 Checking for configuration file "/tmp/app/.yarnrc".
verbose 0.263 Checking for configuration file "/tmp/.yarnrc".
verbose 0.264 Found configuration file "/Users/[user]/.yarnrc".
verbose 0.264 Checking for configuration file "/Users/.yarnrc".
verbose 0.265 current time: 2018-04-27T05:11:53.672Z
[1/4] 🔍  Resolving packages...
verbose 0.401 Performing "GET" request to "https://registry.yarnpkg.com/uuid".
verbose 0.545 Request "https://registry.yarnpkg.com/uuid" finished with status code 200.
[2/4] 🚚  Fetching packages...
[#################################################################################################################################################################################################################################] 834/835Q

The process died after fetching packages, there is no yarn errors file generated.

Tried --ignore-engines, didn't work.

Filed a separate issue for this error: #5761

@sanex3339
Copy link

sanex3339 commented Apr 27, 2018

Same here, can't build with travis-ci on stable node 10.

error [email protected]: The engine "node" is incompatible with this module. Expected version ">=4 <=9".

@Turbo87
Copy link

Turbo87 commented Apr 30, 2018

@sanex3339 that is an issue of upath, not of yarn

yarn works fine on Node 10

@richseviora
Copy link

+1 on Yarn & Node 10 working fine, the only issue I've seen is the upath issue, which I resolved by upgrading chokidar.

@markdavies
Copy link

markdavies commented May 2, 2018

@sanex3339

You can fix this by re-installing:
rm -rf node_modules/
rm yarn.lock
yarn install

This will use upath 1.0.5 which resolves the issue

@BYK
Copy link
Member

BYK commented May 3, 2018

Yarn also has some clean up to do, which is tracked in #5477. Closing in favor of that.

@RKushnir
Copy link

RKushnir commented May 4, 2018

@markdavies Do you know yarn.lock exists for a reason? It's not just that file which you delete whenever there's a mysterious problem.

@scf4
Copy link

scf4 commented May 21, 2018

I had this issue after upgrading Yarn. Opening a new terminal window fixed it.

@oshalygin
Copy link

Any progress on this?

@richseviora
Copy link

@oshalygin this issue is closed; what progress are you looking for? The error message is caused by an older version of upath and upgrading fixes the problem. Is there something missing?

@GabeDuarteM
Copy link

@oshalygin If you don't use upath and you are receiving this error, probably a dependency you have is using it, so indirectly you still have it installed.

What I'm doing to solve it on my projects is to just open up the yarn.lock file and delete the upath portion. That way, yarn will see that there is a dependency not present inside yarn.lock and install the latest version needed for it (a.k.a. the version with this problem solved).
No worries, as far as I noticed, the rest of the yarn.lock dependency versions remain the same.

@alexdevero
Copy link

alexdevero commented May 31, 2018

Please, 🔒 this issue. Can you @torifat?

@p3x-robot
Copy link
Author

i opened it, but i cannot lock it

@yarnpkg yarnpkg locked as too heated and limited conversation to collaborators Jun 1, 2018
@BYK
Copy link
Member

BYK commented Jun 1, 2018

Locked. Please follow #5477.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests