4 ms·
There's a significant misconception in this article: Today, the fate of a module is decided by NPM the company, and they are not afraid of deleting you
by femto113 11y ago
There's a significant misconception in this article:
Today, the fate of a module is decided by NPM the
company, and they are not afraid of deleting your
module and letting someone else have it.
This is not what happened in the recent case, it was the author who deleted (unpublished) the module after the name (and the right to publish future versions) was taken away. If he hadn't unpublished them the already published versions would have stayed around indefinitely.
- diggan 11y agoI'm not very interested in what happen with the kik module and whatnot, more interested in the fact that that can happen. With that said, npm did pull the ownership of kik. Think what you want to think about that, I think that shouldn't be possible. That the author removed his own dependencies is true and you're right. The text doesn't convey that good enough and I will improve it. Thanks a lot for the feedback.
- diggan 11y agoMight be interesting for you to know that I've updated the website and removed that part.