11–20 of 54 posts
> Yarn often produces yarn.lock files that are invalid when you run add, remove, or update. This has never happened to us with heavy daily usage. It's one of the things that remains reliable about Yarn. Would appreciate more details on what exactly happened.
I don't know why, but any time I install something specific in this project:
npm i -D @types/tacos
(for example)
The last line of npm says this: added 9 packages and removed 15 packages in 9.69s
Those 15 removed packages? Not dependency conflicts, no, thats the git dependency and all of its sub-dependencies.
So my workflow is now:
npm i --save
npm i
> Yarn often produces yarn.lock files that are invalid when you run add, remove, or update. This has never happened to us with heavy daily usage. It's one of the things that remains reliable about Yarn. Would appreciate more details on what exactly happened.
I love npm, but there's some bug that keeps looming. I have a git based dependency (basically a dependency that's attached to https://user:password@gitlab.com/xxxxxx#branch ) I don't know why, but any time I install something specific in this project: npm i -D @types/tacos (for example) The last line of npm says this: added 9 packages and removed 15 packages in 9.69s Those 15 removed packages? Not dependency conflict…
I love npm, but there's some bug that keeps looming. I have a git based dependency (basically a dependency that's attached to https://user:password@gitlab.com/xxxxxx#branch ) I don't know why, but any time I install something specific in this project: npm i -D @types/tacos (for example) The last line of npm says this: added 9 packages and removed 15 packages in 9.69s Those 15 removed packages? Not dependency conflict…
The registry is something everyone has to use because npm has a monopoly. It's not open source and is making money for a for profit company. I'm very disappointed to see Node.js is still shipping this anti-foss OSS with its executables :(
I love npm, but there's some bug that keeps looming. I have a git based dependency (basically a dependency that's attached to https://user:password@gitlab.com/xxxxxx#branch ) I don't know why, but any time I install something specific in this project: npm i -D @types/tacos (for example) The last line of npm says this: added 9 packages and removed 15 packages in 9.69s Those 15 removed packages? Not dependency conflict…
" rel="nofollow">https://github.com/pnpm/pnpm>
It centrally downloads all of the modules and then "symlinks" them into your `node_modules` folder.
This is nice because one, it uses less disk space, two, if you've already downloaded a package at a particular version it links it out of the local repo.
Also uses shrinkwrap to handle package locking.
> Yarn often produces yarn.lock files that are invalid when you run add, remove, or update. This has never happened to us with heavy daily usage. It's one of the things that remains reliable about Yarn. Would appreciate more details on what exactly happened.
Our experience has been yarn is fast and reliable.