News for hackers. Stuff that matters.

A comment on Yarn's Future – v2 and beyond. Parent comment

Re:Yarn's Future – v2 and beyond by azangru on Thursday January 24, 2019 @12:50PM (#18991013)
Because npm is a standard (default) package management tool that comes with node.

After getting `package-lock.json` and `npm ci`, I would rather wonder why choose yarn instead of npm.

[ Parent | on HN ]
Re:Yarn's Future – v2 and beyond by MehdiHK on Thursday January 24, 2019 @01:16PM (#18991281)
"npm ci" deletes node_modules directory every time. Try using that when you depend on some native modules. :(
[ Parent | on HN ]
Re:Yarn's Future – v2 and beyond by azangru on Thursday January 24, 2019 @03:31PM (#18992611)
I thought `npm ci` is more suited for ci machines, where it's crucial that packages are pinned to specific versions. For local development, I just npm install. Perhaps with no-save option in order to avoid updating package-lock. Works fine.
[ Parent | on HN ]
Re:Yarn's Future – v2 and beyond by eknkc on Thursday January 24, 2019 @02:36PM (#18992114)
Because I don’t trust it. Had to do rm -rf node_modules too many times with npm.
[ Parent | on HN ]