Hey look, npm broke my project again. Surprise!

Code and dependencies on my local machine, all untouched for a couple of weeks, no longer works. I've no idea how it even managed that.

Oh, and `npm update` crashes.

eventually solved by upgrading npm and running `npm update --depth 500` because some arbitrary child dependencies changed without updating the parent packages, ofc. on my local machine. without me having run `npm update` for about a month.

because of course that makes sense.
Second time in two months, too.

isn't npm great?

You can try Yarn it does have a lockfile which links specifically to the versions used when you ran yarn install. I had the same issue recently, yarn solved it. I heard that npm also added such a feature.

@AlexDeLarge

No, I haven't. Next time this happens (because I'm sure it'll happen again) I'll try it.

There were several packages that needed updating. lodash, Sass, some Spanish-localization (???); a few others. Very strangely, during building, Sass complained it was incompatible with my system despite having worked a few weeks' prior. I hadn't even entered the project's directory since, so I'm very confused as to how the project no longer built. As far as I know, I don't have any globally-installed npm packages, so I really have no idea how this could happen, let alone twice.

@total4ever

I've heard nothing but good about Yarn. I'm playing with it in personal project on the rare occasion I make some free time! but yes, npm has a lockfile, too, and interestingly it didn't help in this case. Considering the above, I'm stumped!

@spacemarshall but. I didn't update any of the dependencies. I hadn't even looked at the project 'twixt it building and it breaking.