4 ms·
I’ve seen zero issue with npm locally or in production (have more issues with Webpack tbh) What kind of problems?
by abritinthebay 9y ago
I’ve seen zero issue with npm locally or in production (have more issues with Webpack tbh)
What kind of problems?
- dikaiosune 9y agoThere are a bunch of linked issues at https://github.com/nodejs/node/issues/13815 https://github.com/nodejs/node/issues/13815 and https://github.com/npm/npm/issues/16991 https://github.com/npm/npm/issues/16991, such as https://github.com/facebookincubator/create-react-app/issues/2558 https://github.com/facebookincubator/create-react-app/issues....
- 0x0 9y agoI've had major trouble with the fact that the new package-lock.json doesn't sufficiently lock versions. In one working copy you can run "nom install" and everything works with no files or package-lock being changed. Yet, in another clean checkout, "npm install" brings in a different set of dependency versions despite having a -lock file, and things start to break. Yarn's yarn.lock seems to get this right.
- tuananh 9y agoany chance that you did `npm install --production` maybe? i think the lock file might be different for that case.