Checkin or ignore .yarnrc.yml?

[truh]

I've just switched one of my projects to yarn-berry and I'm unsure whether the .yarnrc.yml is better checked into version control or .gitignore.

Currently it's in .gitignore and my .yarnrc.yml contains only auto-generated values:

nodeLinker: node-modules

yarnPath: .yarn/releases/yarn-4.9.1.cjs

The nodeLinker values seems quite important for the project as it doesn't build with pnp (I already had to figure this out with another developers computer today) but I'm not a fan of having the yarnPath in the repo. Also I didn't create the file on purpose and I'm worried about accidental changes that might break the project for other people.

[clemyan]

The project .yarnrc.yml should include (and only include) project-specific settings, and thus should generally be committed and shared across all developers working on the project. Per-developer settings should go to $HOME/.yarnrc.yml instead.

Additionally, to avoid discrepancies, all developers should be using the same Yarn version when working on the project. Yarn's native way of doing so is to commit the yarn binary into the repo, and manage versions using yarnPath and yarn set version. If you don't like that, you should use something external to Yarn to manage Yarn versions. The only officially supported tool for that is Corepack, though we are exploring alternatives.