News for hackers. Stuff that matters.
Re:Npm's real problem wasn't the code, but how it's develope... by sli on Friday February 23, 2018 @05:28PM (#16450179)
> Still, others point out that the npm blog announcing 5.7.0 certainly reads like an official release announcement.

Ok, granted, this much is true. But so far as I know, you'd have to be using npm@next to have gotten 5.7.0, not just the regular npm package. I'll fully agree that npm should not have introduced a bug like this, but how great of an idea is it to run bleeding edge versions in production?

There are no comments on this comment yet.