News for hackers. Stuff that matters.
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by notatoad on Sunday January 09, 2022 @06:12PM (#29868416)
you mean roll back package-json.lock or package.json? yeah, but thats not really what i want. maybe my process is crazy here, but this is how i update dependencies:

on a somewhat regular basis, as time allows, i run npm update to bring all my dependencies to the lastest version. then i test (including thorough manual testing / qa), commit, and release with updated dependencies. if some update is broken and i don't have time to fix it then yeah, i can roll back. but the point is to be on relatively up-to-date version of as much as possible, so if something is broken then it turns into a game of trying to figure out which library it was that broke things. i don't want to just not update any dependencies because something is broken.

Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by cerved on Sunday January 09, 2022 @07:03PM (#29868857)
I'm confused. You're looking for a way to go back to the last good version. By your methodology wouldn't that be before you last updated? Or are you looking for a curated service?

A reasonable maintainer semvers their packages.

You shouldn't update to the latest version if you want to minimize the likelihood of issues. That's what stable releases are for