I'll skip to showing you what my package.json looks like. I'm going to skip a few steps here because I'm going to assume you know how to do some of these. Configure package.json in a separate application to point to that repo.Create a Git repository (in this case, mine is in GitHub).The steps to complete this are as follows. The nice thing about using npm to manage your packages is that you can install everything with one command along, and it’ll only give you the files that you need to import. A complete configuration for proxying the default npm registry is visible in Figure 16.1, Proxy Repository Configuration for the npm. The official URL for the main npm registry is. But it can even be a repository that isn’t public. The Remote Storage Location has to be set to the URL of the remote repository you want to proxy.

It really doesn’t matter which one you use. Here’s the short answer: Use a Git repository. I think I found the cheapest most elegant solution, and I hope you can benefit from what I’ve learned. If this is not the case then NPM will cause you many headaches.Have you found yourself like me scouring the internet for the cheapest easiest way to do something? I spent a few hours digging into finding a way to host, deploy, and install a package using npm but without using npm. It is possible to configure HTTPS access to the repository as long as you are using proper certificates, or your clients implicitly trust your internal CA. Run: npm config set npm login this NPM will use your private registry for publishing and downloading your scoped packages and use the official registry for everything else. To make life super easy you should scope your private packages (TLDR: prefix the name with in the package's package.json). Refer to Verdaccio's excellent documentation for more information. Your container will mount conf/ and storage/ directories for persistent state. Inspect the file to see what it will do (always a good idea) and then run: make run We will be using the Verdaccio server and we will run the server inside a Docker container.ĭownload this Makefile into the directory that will house your registry on your Docker host. In this situation you may want to set up a private NPM registry and publish your packages there, for re-use by your internal applications. While open source is great, sometimes it is not possible to make your code public and publish it to the official NPM registry.

Npm config set private registry