Run install again, and your project should be up and running. NPM will still be communicating with the default registry, and with throw an error on NPM install of the private package. And now all your developers can use it, not exactly. Let’s say your company has created a Node package that contains proprietary information, or for some other reason you don’t want it to be public. So we will skip over that and get right to a use case. Creating a private registry is another post for another day. and then set your internal CouchDB as the registry config, then youll be able to read any. However there are situations where a private registry is needed. Does npm send any information about me back to the registry. This global setup will allow any of your projects to use the Font Awesome package and your token. You can set this up globally or per-project. For most projects, the public registry is exactly what you need, and is the default registry of NPM. Now that youve got your package token handy, youll need to configure the fortawesome scope to use our Pro npm registry. We’ve all used NPM before, but where is all that information coming from? Enter the NPM registry, which allows for packages to be resolved by name and version, allows for package publishing, and user account management.

Npm config set registry back to default