←back to thread

2525 points hownottowrite | 1 comments | | HN request time: 0.202s | source
Show context
Aozi ◴[] No.21190660[source]
What we need is a JS developer to take down an important package from NPM in protest, thus breaking the Internet again.
replies(2): >>21190743 #>>21194973 #
byte1918 ◴[] No.21190743[source]
The NPM fiasco should no longer be possible

If you want to unpublish a package after 72 hours have passed, contact npm Support. For more information about why we don’t allow users to unpublish packages after 72 hours, see our unpublish policy.

https://docs.npmjs.com/unpublishing-packages-from-the-regist...

replies(4): >>21190798 #>>21190801 #>>21190806 #>>21191523 #
leppr ◴[] No.21190801[source]
It was never possible without "admin" intervention. That whole inccident was NPM's sole responsibility.
replies(1): >>21192982 #
minitech ◴[] No.21192982[source]
That’s… plainly wrong. `npm unpublish --force your-package` would really just unpublish your package.
replies(1): >>21198323 #
1. leppr ◴[] No.21198323[source]
Okay that's embarrassing thanks. Hard to believe it took so long before being the left-pad debacle happened.