I tried updating my teams frontend pipelines from Yarn 1 to Yarn 2 since there seemed to be some significant performance improvements.

I spent some time trying to understand why I needed a third party plugin to run the equivalent of `yarn install --production` I just said fuck it and I'll let the frontend team figure this shit out.

So yeah, I wouldn't be surprised if the Yarn 1 usage is significantly higher than Yarn 2

The only project of mine where I use Yarn 2 was one where arcanist, the yarn2 maintainer, added it himself. Otherwise, I use yarn@1 which requires significantly less brain cells than following yarn2 opinions/changes/plugins/installing

Still on Yarn 1.

Looked at Yarn 2, saw that it was a ton of work (compared to our npm -> yarn 1 transition) and said sod it.

Let's see if Yarn 1 -> 3 is any easier.

We also remained on Yarn 1 because developing packages using the workspaces feature is really nice.

We did make an attempt at moving to Yarn 2, it did not work out well. At that time (probably 12 months ago or more) lots of upstream packages had broken package.json files, we never managed to fix them all. Lots of things with React were a bit screwy too!

Still on Yarn 1 with no plans on upgrading anytime soon.