Makes sense. One obvious power feature, that not only doesn't affect normal users, and would be well worth the money, is a locked down priority server. With npm being an open registry, any author can overwrite any release at any time. I don't want that possibility to happen on production, so if they provided a server with the versions you are using frozen from the general community, I would be interested in that.
You can specify what version you want.
That doesn't necessarily imply that version will continue to be available.
Ruby has the same problem with "yanked" versions of gems.
Comments
Makes sense. One obvious power feature, that not only doesn't affect normal users, and would be well worth the money, is a locked down priority server. With npm being an open registry, any author can overwrite any release at any time. I don't want that possibility to happen on production, so if they provided a server with the versions you are using frozen from the general community, I would be interested in that.
Well, you can already specify a particular version that you want to use (though I'm not sure if you can verify that using hashes).
You can specify what version you want. That doesn't necessarily imply that version will continue to be available. Ruby has the same problem with "yanked" versions of gems.
You cannot (verify using hashes that is). On the other hand, you can use git URLs with commit hashes, which works pretty well.