|
|
|
|
|
by ricardobeat
2948 days ago
|
|
I wonder if they ever tried `yarn --pure-lockfile` to avoid updating the lockfile unnecessarily? > We never observed install inconsistencies when using npm previously Interesting, since NPM has had issues being deterministic since package-lock came to be, and this was one of the main reasons yarn was created. The fact that yarn has a healthy community, actually accepts contributions, and encourages public discussion is a big pro for me (colored by personal experience). |
|
NPM error: ~probably not our fault, there might be additional output above
Yarn error: ~an error has occured, here's what you'd do if you think it is a bug
NPM is probably correct most of the time but the difference in attitude felt striking to me.