Thread by @wojtekmaj91

@dmitriid @daniguardio_la @DennisKortsch @AdamRackis 🧵 My top reasons to update:
1. It's fast! Especially when working in complex monorepos, where Yarn v1 was struggling, Yarn v2/v3 improves performance by *orders of magnitude*.

@dmitriid @daniguardio_la @DennisKortsch @AdamRackis 2. Zero-installs/checkoutable cache - eliminates the need of handling auth tokens for installing internal packages. Only the person installing/updating the internal package has to have an auth token - the rest of the team, and the CI, doesn't need to have any additional creds.

@dmitriid @daniguardio_la @DennisKortsch @AdamRackis 3. "Normalized shell" - forget about cross-env, Unix-style env variables in scripts ✨ just work ✨ on Windows machines. Just like "&&", "||" and other fun stuff.

@dmitriid @daniguardio_la @DennisKortsch @AdamRackis 4. patch: protocol - this made patching dependencies easier than ever. I'm using it to reliably patch lucide-react to be able to use SVG icon pack in React Native, which otherwise wouldn't be possible. See: github.com/lucide-icons/l…

@dmitriid @daniguardio_la @DennisKortsch @AdamRackis 5. Built-in dedupe command ensures I'm not getting duplicated dependencies - unless, of course, it's absolutely necessary.

@dmitriid @daniguardio_la @DennisKortsch @AdamRackis 6. Everyone working on the same repo are on the same version - using incl. binary or Corepack (highly recommend). Many of the issues we've had with package managers in the past were because of old versions used by some team members. This eliminates the issue.

@dmitriid @daniguardio_la @DennisKortsch @AdamRackis CC @arcanis if you want to use any of it for "Why should you migrate?" section feel free!

@dmitriid @daniguardio_la @DennisKortsch @AdamRackis 7. Yarn Plug'n'Play, although still gaining traction & struggling with some compatibility problems, rewards you with even better performance, about 60% disk space savings and the possibility to use Zero-Installs.