Open JoshuaKGoldberg opened 5 months ago
I filed an issue with corepack about this https://github.com/nodejs/corepack/issues/507
As I write in the issue description, a workaround is to use corepack yarn
instead of just yarn
. And corepack yarn build
, corepack yarn rebuild-test-project-fixture
etc.
I'll give the corepack people some time to to reply to my issue before I decide what the best way forward here is
I had the same issue, but it finally works after using a new terminal session.
What's not working?
I tried setting up a new repo locally and on github.dev on a pairing session with @Tobbe today. I went through the instructions in CONTRIBUTING.md:
https://github.com/redwoodjs/redwood/blob/a685bd424ae3beb5f94173fd4815ebe6b68fe190/CONTRIBUTING.md?plain=1#L58-L61
...but Yarn is still using my local 1.x version:
How do we reproduce the bug?
corepack enable
andyarn install
What's your environment? (If it applies)
I copied this from another issue I filed recently:
...because trying to run the command in my local repo gives:
Are you interested in working on this?
I've hit confusing issues with Yarn versioning before (https://github.com/yarnpkg/berry/issues/4426) and have no interest in working on this myself. 😄