It also lets you choose between using NPM or Yarn to install components or (and this is the neat part) use its own CLI tool to import components. The most popular private NPM registry for front end developers (IMHO) is Bit.dev (it is in fact a combination of three things: A private NPM registry, a documentation site, and a CLI tool for publishing components).īit.dev lets you decide whether you’d like to make your packages (front end components) available for everyone or just those with the right permissions. A Private NPM Registry - Bit.dev as an example of what’s possible The most common registry that open source developers and organization across the world use is public NPM registry but it is not the only registry we have. NPM registry is the database of javascript packages which comprise of software and its metadata, can also be versioned just like Git. Most of the organizations and top businesses generally prefer to have their own NPM registry to store their own private javascript code and can semversion them similar to every npm package. We can also use this registry for publishing private packages.

In this post, we will learn about setting up NPM Registry for local development.

Npm config set registry default