4 ms·
On top of the really different API, you always get v1 when you install (which I never understood). You need to upgrade manually everywhere with a command line.
by h1fra 3y ago
On top of the really different API, you always get v1 when you install (which I never understood).
You need to upgrade manually everywhere with a command line.
If I had to bet: most user didn't even bother upgrading because they are not aware of this behavior.
- evtothedev 3y agoI am learning this just now from this comment, so I think you are right.
- sli 3y agoSame here. I haven't done frontend in a few years now but I was shocked when the top comment was saying most people don't even use Yarn 2. I had no idea Yarn was past 1.x.
- k__ 3y agoI like that Yarn 4 is installed into the project directory. This way you always have the right version when cloning a random Yarn repo.
- orra 3y agoAlways having the right version is nice. However, you can get similar benefits with a shorter bootstrap script. Personally I prefer this because there's less third party code duplicated directly to your own repo.
- orra 3y ago> you always get v1 when you install (which I never understood) Yeah, they really wanted you to install yarn's source to your repo, which is why they don't let you `npm install` yarn v2 (or higher). That's maybe great for monorepos, but personally I find it ugly. Thankfully now you can use `corepack`, which is shipped with npm. This way you can specify a version of yarn in packages.json, in the `packageManager` field. That is, without committing yarn's source to your repo.