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 #502
Comments
Found the problem - the v1 has a bug where it spawns the file pointed by That causes the checked-in v2 binary to be executed via the |
Will be fixed by yarnpkg/yarn#7592 |
Closing, the fix got released in the 1.19.1 👍 |
Great, thanks!
…On Tue, Oct 15, 2019, 10:22 Maël Nison ***@***.***> wrote:
Closed #502 <#502>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#502?email_source=notifications&email_token=AAEUHBJIIC3R6LUIH5DQMATQOVVSJA5CNFSM4I4PEAC2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUGZIJWQ#event-2712831194>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEUHBNCGVFFFBTCWPHLZNLQOVVSJANCNFSM4I4PEACQ>
.
|
Describe the bug
In Yarn 2 child processes are run with Node.js interpreter from
PATH
, not with the Node that is running Yarn itself.To Reproduce
Yarn 2 (
yarn set version from sources
)Works correctly in Yarn 1:
Environment if relevant (please complete the following information):
The text was updated successfully, but these errors were encountered: