Congrats to @arcatek for this! The key value proposition of yarn for us is:<p>- 15x installation speed, from 1400s with NPM to 90s with yarn PnP (Yes the gap is that big!)<p>- Catching a lot of badly declared dependencies that NPM would silently let pass, before blowing up on us in production<p>- Manage and organize our monorepo efficiently, including in CI<p>There are still some rough edges, mostly due to other packages of the JS ecosystem applying bad practices (looking at you storybook!) or even flat out errors about dependency management, and yarn is pretty strict with that, which is a good thing in the long term.<p>We have been using yarn with PnP for around a year now on a monorepo of around 160 packages, and it has been a life saver for the engineering team, allowing us to scale JS development effectively.<p>(edit typo)