News for hackers. Stuff that matters.

A comment on NPM registry prank leaves developers unable to unpublish packages.

Re:NPM registry prank leaves developers unable to unpublish ... by chaboud on Wednesday January 03, 2024 @10:08PM (#38862524)
The circular dependency problem is kind of "90's interview question" easy (source: I was asked this in an interview in the 90's). What other comically obvious lessons remain to be painfully learned for npm folks?
[ Parent | on HN ]
Re:NPM registry prank leaves developers unable to unpublish ... by internetter on Wednesday January 03, 2024 @10:22PM (#38862586)
We'll see if there is any real policy change. I hope there is, at the very least to avoid another instance of this mistake, but also to prevent genuine targeted abuse of this policy failure.

For now, NPM is slowly taking all the packages down, and GitHub has forcefully made the org private: https://imgur.com/a/WuSpBQi

[ Parent | on HN ]
Re:NPM registry prank leaves developers unable to unpublish ... by RamblingCTO on Thursday January 04, 2024 @08:03AM (#38866491)
The worst thing is that this already happened in January 2023. NPM again showing that only the brightest of the brightest are working on this ecosystem o7
[ Parent | on HN ]
Re:NPM registry prank leaves developers unable to unpublish ... by internetter on Thursday January 04, 2024 @08:42AM (#38866861)
As far as we know, NPM's solution was to flag the organization (making the links to the issues within the article useless) and to remove the packages without any policy change.
[ Parent | on HN ]
Re:NPM registry prank leaves developers unable to unpublish ... by exabrial on Thursday January 04, 2024 @08:27AM (#38866720)
Because node is a comedy. It’s intentionally making a very easy problem into a Rube Goldberg machine.
[ Parent | on HN ]
Re:NPM registry prank leaves developers unable to unpublish ... by intunderflow on Thursday January 04, 2024 @08:58AM (#38867013)
They won't learn anything from this, they'll blame the authors for "using NPM wrong" just like the dogpiling comments were on the everything repo before mass flagging by the same people booted it off GitHub.
[ Parent | on HN ]