My own experience is that Yarn 2/3 have worked great, as long as you stick with the "`node_modules` linker" option rather than the "PnP/Zero Install" option.
I looked into switching to yarn for the first time earlier this year, since I was having minor multi-platform issues with npm and was pretty sure yarn could fix them. Since the docs seemed to make PnP/Zero Install the "blessed path," I tried to go with that. I quickly became confused at the correct way to configure certain aspects for my org in conjunction with our build pipelines, decided it was way too much unnecessary complexity to teach to my org, and kept our npm setup.
Getting it to auth properly with GCP artifact repository in GitHub actions was a bit of a pain. Conflicting documentation between Google, Yarn and GitHub didn’t help.
But isn't that nearly defeating the entire point of the newer versions? They basically tried to go around the entire ecosystem, and having to not use the main feature that drove the development of yarn berry just seems like proof that it was a mistake.
There's other improvements too. Anecdotally I've seen Yarn 2+ install faster than Yarn 1. The UI output is more informative. The workspace behavior has been pretty solid. The "install Yarn 1 globally, Yarn 2+ per-repo" bootstrapping behavior is a bit quirky, but it does make it nice that everyone using the repo is using the same Yarn version for actual execution.
I like the _idea_ of PnP conceptually, but my experience was that there's too many other tools that depend on having `node_modules` on disk for things to work out okay.
