npm-release | Making releasing to npm so easy a kitten | Build Tool library

npm-local npm-release local npm-generic-local are all local repositories from my understanding. You can publish and download packages from local repositories in Artifactory.

However, npm-central is a remote repository that is pointing to npmjs.com. Remote repositories allows you proxying an upstream (in this case npmjs) but they won't allow you publishing new packages to it.

You want to be able to both publish and resolve (i.e. download) packages from a single repository and this is where virtual repositories come into play.

Virtual repositories allow you aggregating one or more local, remote and even virtual repositories in a single repository and by that, allowing you access to all of your packages in all of the aforementioned repositories. It will allow you both downloading and publishing of packages.

Therefore, I suggest creating a virtual repository > aggregate npm-local and npm-central for example (you can add all of the remote and local repositories you have added) > specify the Default Deployment Repository which is the local repository in which published packages will be stored in (i.e. when you use the 'npm publish' command) > update your .npmrc file (don't forget to do 'npm login' to the new virtual repository).

This way, you will have a single (virtual) repository allowing you downloading packages from npmjs (and the packages in your local repositories) and publishing packages to the local repository you selected.