News for hackers. Stuff that matters.
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by umvi on Sunday January 09, 2022 @06:10PM (#29868397)
Rollback what? You can't rollback someone else's dependencies.
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by kristjansson on Sunday January 09, 2022 @10:46PM (#29870355)
But you can roll back your dependencies until your entire dependency graph avoids a bad version.
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by umvi on Sunday January 09, 2022 @10:48PM (#29870369)
Yeah but in this case you might not be directly dependent on colors. You might be dependent on http-server, which is in turn dependent on colors. You can only roll back http-server, and unless http-server rolls back colors, you are stuck.
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by kristjansson on Sunday January 09, 2022 @11:40PM (#29870730)
So set it in overrides? Blacklist it in your private mirror? It’s your project, your environment, and your computer, you’re never stuck.
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by umvi on Monday January 10, 2022 @12:42AM (#29871057)
Oh I agree, nobody is stuck. I'm just pointing out that, sure, there are messy workarounds, but in this case it is not as simple as "rollback".
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by cerved on Sunday January 09, 2022 @06:45PM (#29868700)
Your source code obviously
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by umvi on Sunday January 09, 2022 @06:58PM (#29868805)
In this case, the problem isn't in your own source code, it's in someone else's source code.
Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by cerved on Tuesday January 11, 2022 @02:38PM (#29896673)
but package.json and package_lock.json presumably are