←back to thread

2525 points hownottowrite | 1 comments | | HN request time: 0s | 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 #
celticninja ◴[] No.21190798[source]
Could you just publish garbage instead?
replies(2): >>21190867 #>>21190869 #
yoz-y ◴[] No.21190867{3}[source]
You could but everybody uses version pinning in production, right?
replies(2): >>21190928 #>>21191443 #
emsy ◴[] No.21190928{4}[source]
People who are serious about reproducible builds host their own repos. Most people probably don’t know the difference between ^1.0.1 and ~1.0.1
replies(1): >>21191115 #
1. bakuninsbart ◴[] No.21191115{5}[source]
Thanks for making me look that up!