-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Bug] Yarn 2 should run child processes with the same Node #1766
Comments
Thought we fixed this in #1403 🤔 |
@merceyz Ooops, I'm sorry, actually the issue targeted Yarn version 2.1.1-git.20200806.1b11fbd5 (version from https://github.com/facebook/jest as of now), not Yarn 2.1.1. |
2.1.1-git.20200806.1b11fbd5 is newer than 2.1.1 so if it doesn't work with that it's a regression |
Interestingly, it works correctly after
|
They should both be the same |
@merceyz You're right, they are the same. Looks like this issue is caused by
|
Ah, that's a issue in how V1 spawns Yarn. It was fixed in yarnpkg/yarn#8144 but the CI is broken for V1 so it hasn't been released yet |
The fix has been released in V1, update your global Yarn version and the |
@merceyz It works now correctly. Thank you! |
Describe the bug
Actual: Yarn 2 uses
node
fromPATH
when executingyarn node ...
Expected: Yarn 2 should use the Node that is running Yarn itself when executing
yarn node ...
To Reproduce
Configure Yarn 2.1.1:
Expected output of the last command is
v12.16.1
Works as expected with Yarn 1:
Environment if relevant (please complete the following information):
Additional context
There is an unpleasant consequence: when
node
is not inPATH
,yarn node ...
cannot be run:This caused https://youtrack.jetbrains.com/issue/WEB-46371.
The text was updated successfully, but these errors were encountered: