Yarn itself is saved into the repo, so the only external dependency is nodejs. I've had a small number of packages have issues with the zip format, which is solved by setting unplugged (very well documented).Ī user clones the repo and they are done. Dependencies can have conflicting dependent packages. yarn/cache folder (equiv of node_modules) to git (via git-lfs). That is because I have not gone against the default of 0-config repos, that is saving the. Since I migrated everything to yarn 2 its been a breeze, my other contributors have been able to completely forget about it (as it just works) and I've been able to assert that everything that works today will work in six months and two years. I run about ~30 JS repos, ~10 of them monorepos. I'm grateful to the Yarn project for pushing NPM in the right direction, and wish it and its remaining users all the success in the world, but I no longer see an urgent need in the ecosystem for Yarn to exist and would no longer recommend it by default for any greenfield project. Performance and reliability have been notably better in my experience (keeping in mind that my baseline for comparison is a release of Yarn from two years ago). Luckily, the stable release of NPM 7 arrived just in time for us to switch over with minimal hassle. At that point, it was untenable for us to continue relying on a broken, unmaintained tool for such a critical function.
#Yarn zero install update
Meanwhile, the old release of Yarn 1.x that I'd pinned in order to work around a blocker regression (v1.21.1) was starting to show its age, and eventually became unusable after a third-party package update triggered another hidden blocker bug in that release (which, IIRC, the team had elected not to fix because only 1.x was affected). Yarn >=2 is probably fine for what it is, but I wasn't prepared to invest resources into rearchitecting how we handle dependencies for nebulous (or possibly negative) benefit. NPM 7 is fantastic, and feels like a worthy successor to Yarn 1.
![yarn zero install yarn zero install](https://prod-content-care-community-cdn.sprinklr.com/d80f176d-2bd5-487b-b539-b24b3ede5ed6/2A020552700448E48DD7692E3EBA94-9b812ada-77f8-417b-9421-2b6f49f75470-38124359.jpeg)
My experience with Yarn 2 was switching to NPM 7.