Closed Andreyco closed 7 years ago
Hey !
Please, remove yarn.lock
and instead push the official lock file of npm
.
Note that this issue of pope
should be fixed soon.
NPM's package-lock.json
is in place already.
Since Yarn is very popular, I think it's desired to keep yarn.lock
for Yarn users.
yarn.lock
guarantees everyone will get same install - package developer and end developer as well.
Please, propose further steps.
To note, when installed using NPM, correct dependency version is installed thanks to package-lock.json
. Essentially, removing yarn.lock
let installing broken dependency for Yarn users.
The answer is to fix the package that is breaking over adding unwanted layers. Yarn is something I do not use and popularity is not a metric to switch tools
The answer is to fix the package that is breaking over adding unwanted layers.
As long as you are an owner of package affecting other package. Would not be that easy if you do not have possibility to fix an issue, of wait ages to get merged.
Yarn is something I do not use and popularity is not a metric to switch tools
I agree popularity is not a metric - quality is. And that's why I care about Yarn users as well as NPM users.
Therefore I strongly believe providing lock file for Yarn users is not unwanted layer, comparing to providing such solution for NPM users.
Notes: only NPM 5 users get benefit of lock file - plus early versions of NPM 5 had problems with lock file. Yarn, on the other hand, understands lock files from day one of it's existence.
Also, introducing
yarn.lock
file, which would prevent this situation.