its basically a way to group your packages per user/organization. You can read more about npm scopes here if you’re not familiar with them. In my case I want only authenticated users to be able to see and publish packages for security reasons, after all it should be private, right? So I’m going to follow this to make it so users are only allowed to publish packages that have the scope prefix in their package name as defined in package.json.You can change the configuration to fit your needs from the conf/config.yaml file, the docs include all necessary information regarding the possible configuration options.In my case I’ll be using the “docker-local-storage-volume” one to store published packages locally on my server through a mounted docker volume. You can clone one of the example repositories here to get started.In the following sections I’ll walk you through how you can setup and configure your own private npm registry.

Verdaccio is a lightweight private npm proxy registry that allows you to have your own npm registry for free. Npm enterprise already offers that however its not free.

This helps achieve modularity, code re-usability and separation of concerns in your codebase. With npm registries you can publish your own npm packages that have their own release cycle so that anyone with access to the registry can install and use in their own projects. Sometimes you want to share code, libraries or components across your projects or organisation, but don’t want your npm packages to be public.

Npm config set to non secure http