News for hackers. Stuff that matters.

A comment on State of React Native 2018. Parent comment

Re:State of React Native 2018 by megaman22 on Friday June 15, 2018 @01:42AM (#17317739)
I'm borderline infuriated that this isn't the default way that npm works. Maybe if people didn't willnilly break things and followed semver, it'd be okay, but I waste too much time bisecting why some package that used to work is blowing up my build or failing in less obvious ways.

But I'm a crusty almost-30 .Net developer used to Nuget.

[ Parent | on HN ]
Re:State of React Native 2018 by allover on Friday June 15, 2018 @04:13AM (#17318259)
npm does maintain a lockfile for you by default since npm 5, if that's what you mean.

There really is no reason to be encountering surprise sub-dependency changes with npm.

[ Parent | on HN ]
Re:State of React Native 2018 by megaman22 on Friday June 15, 2018 @06:03AM (#17318641)
Happens all the time when package.json defaults to foo: "^1.2.3", and some bozo does breaking changes in 1.2.5.
[ Parent | on HN ]
Re:State of React Native 2018 by danabramov on Friday June 15, 2018 @10:16AM (#17319912)
If you have a package lock, even caret in package.json won't automatically install it.
[ Parent | on HN ]
Re:State of React Native 2018 by allover on Friday June 15, 2018 @04:40PM (#17323361)
> Happens all the time when package.json defaults to foo: "^1.2.3", and some bozo does breaking changes in 1.2.5.

No it doesn't. Since npm 5, npm is lockfile-by-default, you don't get updates unless you ask for them. Whether one particular package correctly respects semver is irrelevant.

[ Parent | on HN ]