2 ms·
No, the whole point is to not have a central node. However, it is possible that NPM Inc decides in the future to seed all public packages, but not being able t
by diggan 11y ago
No, the whole point is to not have a central node.
However, it is possible that NPM Inc decides in the future to seed all public packages, but not being able to remove ownership of the packages. Or another private company might come along and do that.
If you use an unpopular module, and you want it to exist, you better seed it, somehow.
The es-cli will help with this in the future, allowing you to spread your module across public and private nodes.