Do we need yarn v4?

[rin-st]

Why did I start to think about it? Some people use v4 although we’re configured v3 in our projects. So when using v4 yarn.lock changes and use last versions of packages, not the ones we have in our yarn.lock and things might break. Examples, challenge 0 telegram, challenge1 telegram. But that cases are very rare

---

Yarn v4 overview: https://yarnpkg.com/blog/release/4.0

Pros

• better performance? For me it's not true. yarn install after the fresh clone repo are the same - for yarn v3 (21s 416ms), and v4 (21s 570ms)
• integration of ts and upgrade-interactive plugins by default
• better ui
• last version of yarn, hence yarn team works mostly with it
• some day we will need to migrate anyway

Cons

• v3 already working good for us
• there’s some strange behaviors on v4, for example sometimes yarn v4 should be updated to support newer versions of typescript Typescript 5.5 is not working with yarn v4 and nodeLinker pnp, it forces switching to nodeLinker node-modules microsoft/TypeScript#58950 (comment)

---

To be honest, I'm tending not to change it for now, maybe 60% v3 and 40% v4. But I'd love to know your thoughts on this @carletex @technophile-04

Draft pr to test v4 if you want #961