Dev corrupts NPM libs 'colors' and 'faker', breaking thousands of apps

Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by godDLL on Sunday January 09, 2022 @09:53PM (#29870039)

But completely sane to base your project on a package of code you don't control?

Or to lock up his Github account for exercising his prerogative onto his own code?

His behaviour is unusual, but that, you know, could change easily. It could become the normal just like that. Puff.

[ Parent | on HN ]

Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by prepend on Monday January 10, 2022 @06:10AM (#29873076)

> But completely sane to base your project on a package of code you don't control?

Yes, certainly. I think this is sane because with OSS you can control it if you need to. Until then use what exists. It’s sane to use Linux in my project even though I don’t control that. I suppose it’s also sane to use Windows even though I don’t control that.

[ Parent | on HN ]

Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by godDLL on Monday January 10, 2022 @02:55PM (#29881016)

So you just leave Windows update on in production?

Brave man.

[ Parent | on HN ]

Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by prepend on Tuesday January 11, 2022 @06:12PM (#29899776)

Depending on something doesn’t mean crazy. I depend on lots of OSS projects (and windows), but I have a management system where I control what gets updated and when.

[ Parent | on HN ]

Re:Dev corrupts NPM libs 'colors' and 'faker', breaking thou... by godDLL on Wednesday January 12, 2022 @11:07PM (#29916746)

You control what gets updated and when.

There we are.

[ Parent | on HN ]