What is an npm registry?
The page for a given npm package contains a download link as well as useful metadata about the project, such as:
- The project description and version history
- The code’s author(s) and software license
- Statistics about the number of downloads
What is the difference between public and private npm registries?
npm registries can be either public or private:
- The public npm registry, as the name suggests, is centrally managed by npm, Inc., with packages available to anyone who wants to download them.
- Private npm registries are restricted in terms of who may view and download them. Privately hosted packages are only available to those who have been granted access.
Using private npm registries is highly useful for organizations that don’t want to expose internal software packages to the general public.
Why should I care?
Private npm registries, too, serve an important purpose. Large enterprises can use them for internally facing projects and libraries that need to be distributed to a large number of developers, such as a user interface framework for web development.
[Image courtesy: npm]