4 ms·
> If you contact support, they will check to see if removing that version of your package would break any other installs. If so, we will not remove it. You’ll e
by alanh 11y ago
> If you contact support, they will check to see if removing that version of your package would break any other installs. If so, we will not remove it. You’ll either have to transfer ownership of the package or reach out to the owners of dependent packages to change their dependency.
Wow. A big change. It means publishing on NPM is granting an essentially irrevocable license. (Edit: Not that anything is wrong with that.)
- steveklabnik 11y agoThis is also just pretty much true, due to open source licensing and how it works. I see this as a plain-English clarification more than a significant change in policy. (That is, the part about npm being able to keep your package up even if you want to take it down, not the changes to unpublish generally)
- kibwen 11y agoGiven that they were willing and able to republish left-pad just as it existed before it was taken down, this was already true in practice, though merely selectively enforced.
- steveklabnik 11y agoThat action was described as an exceptional response to exceptional circumstances, I don't believe it had ever been done before. Which doesn't change your point, but is a bit different than 'selectively enforced.'
- profmonocle 11y agoTrue, but most (all?) NPM packages use free software licenses. If you use such a license you've already granted an irrevocable license to everyone. NPM doesn't need your explicit permission to upload the package to begin with. If you want to be selective about who can freely distribute your code, then you shouldn't be using a free software license.
- imtringued 11y agoThis has been in the TOS since NPM existed. Nothing has changed.