'yarn set version berry' requires deletion of .yarnrc.yml

• I’d be willing to implement a fix

Describe the bug

Sometimes I am trying to install berry. I may have copied some config files over to a repo that wasn’t previously using berry, or I may have changed some stuff in a monorepo and, for whatever reason, berry isn’t installed and .yarn is not present.

To Reproduce

Problem 1:

• Attempting to install berry will error if the .yarnrc.yml is present:

> yarn set version berry
node:internal/modules/cjs/loader:928
  throw err;
  ^
Error: Cannot find module '.yarn/releases/yarn-berry.cjs'

• To get around it I use a silly file called .yarn-bootstrap.sh:

#!/bin/sh
mv .yarnrc.yml .yarnrc.yml.bak
touch .yarnrc.yml
yarn set version berry
yarn plugin import workspace-tools
mv .yarnrc.yml.bak .yarnrc.yml

This script should not be needed and berry should be resilient to install without requiring a deleted config file.

Problem 2:

• Plugins specified in the .yarnrc.yml cannot be installed without removing them from the .yarnrc.yml:

> yarn plugin import workspace-tools
Internal Error: Cannot find module '.yarn/plugins/@yarnpkg/plugin-workspace-tools.cjs'
Require stack:
- .yarn/releases/yarn-berry.cjs

An easy version for the user could be for the yarn command to automatically download the berry release and plugins specified in .yarnrc.yml if they are missing.

[icaro-capobianco]

Tools like this shouldn’t require you to add binary files to your repo, config files should be enough

[arcanis]

That expectation is false and it does not even apply here and you can not assume that using a repository with a yarn binary already checked into it is the only thing that I can possibly ever be doing.

I mean, that’s our tool, so if we tell you how to use it but you prefer to ignore recommendations and do differently, it’s fine, but you have to expect that you may not hit the happy path, and thus have to build some additional scripts to get the logic you want.