[Bug] Home config interaction w/ Yarn 1

[borekb]

Describe the user story

If I have:

• ~/.yarnrc.yml (home directory Yarnrc file) with yarnPath pointing to e.g. v1.22.10
• ~/project/.yarnrc.yml (project-level Yarnrc file) with yarnPath pointing to e.g. v2.3.1

Then cd ~/project && yarn --version should yield version 2.3.1, not 1.22.10.

Describe the solution you'd like

Respect the closest Yarnrc file – it should have higher priority / take precedence over my global config.

Describe the drawbacks of your solution

Not sure if home directory's Yarnrc file isn't special somehow. Maybe some people depend on the current behavior?

Describe alternatives you've considered

N/A

Additional context

This was a major gotcha for one of my colleagues today, hard to debug. We were not sure why Yarn "misbehaves" when everything seemed correct. It turned out that there was a yarnPath in the home directory and that has overwritten our project setup.

[arcanis]

The problem isn't in Yarn 2. The global Yarn you have reads yarnPath, then spawns it. I suspect your global Yarn is Yarn 1, and Yarn 1 unfortunately uses its own logic to do that, more as a workaround than anything else. It's a bug, but the fix isn't in this codebase, and it's not clear whether I'll have the time to address that anytime soon 😕

Note that with Corepack this problem won't happen again, since the packageManager field will be extracted by Corepack itself, not Yarn or anything else.

[borekb]

Ah yes, makes sense that this is a Yarn v1 thing, thanks for the explanation.

[yarnbot]

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

[missing1984]

oops, run into the same issue but with yarn 2.