News for hackers. Stuff that matters.

A comment on Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes Current Release Line. Parent comment

Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by abritinthebay on Tuesday October 31, 2017 @04:05PM (#15596088)
I’ve seen zero issue with npm locally or in production (have more issues with Webpack tbh)

What kind of problems?

[ Parent | on HN ]
Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by 0x0 on Tuesday October 31, 2017 @06:29PM (#15597180)
I'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.
[ Parent | on HN ]
Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by tuananh on Tuesday October 31, 2017 @10:31PM (#15598462)
any chance that you did `npm install --production` maybe? i think the lock file might be different for that case.
[ Parent | on HN ]
Re:Node.js 8 Moves into Long-Term Support, Node.js 9 Becomes... by dikaiosune on Tuesday October 31, 2017 @04:17PM (#15596190)
There are a bunch of linked issues at https://github.com/nodejs/node/issues/13815 and https://github.com/npm/npm/issues/16991, such as https://github.com/facebookincubator/create-react-app/issues....
[ Parent | on HN ]