verdaccio is a fork of sinopia. It aims to keep backwards compatibility with sinopia, while keeping up with npm changes.
We are looking for a new logo, ⚡⚡⚡ please 🙏🙏 I encorage you to contribute helping us to decide ⚡⚡⚡
It allows you to have a local npm private registry with zero configuration. You don't have to install and replicate an entire database. Verdaccio keeps its own small database and, if a package doesn't exist there, it asks any other registry (npmjs.org) for it keeping only those packages you use.
If you want to use all benefits of npm package system in your company without sending all code to the public, and use your private packages just as easy as public ones.
If you have more than one server you want to install packages on, you might want to use this to decrease latency (presumably "slow" npmjs.org will be connected to only once per package/version) and provide limited failover (if npmjs.org is down, we might still find something useful in the cache) or avoid issues like How one developer just broke Node, Babel and thousands of projects in 11 lines of JavaScript.
If you want to use a modified version of some 3rd-party package (for example, you found a bug, but maintainer didn't accept pull request yet), you can publish your version locally under the same name.
See in detail each of these use cases.
- Node.js >= 4.6.1
npmoryarn
Installation and starting (application will create default config in config.yaml you can edit later)
npm install --global verdaccioRun in your terminal
verdaccioAfter npm 5.2 you can use npx which install and launch verdaccio with the same command
npx verdaccioYou would need set some npm configuration, this is optional.
$ npm set registry http://localhost:4873/
# if you use HTTPS, add an appropriate CA information
# ("null" means get CA list from OS)
$ npm set ca nullNow you can navigate to http://localhost:4873/ where your local packages will be listed and can be searched.
If you are an adventurous developer you can use and install the latest beta version, this is a non stable version, I'd recommend only use for testing purporses.
$ npm install -g verdaccio@betanpm adduser --registry http://localhost:4873npm publish --registry http://localhost:4873This will prompt you for user credentials which will be saved on the verdaccio server.
When you start a server, it auto-creates a config file. For instructions on how to run Verdaccio as a service, with a nice URL or behind a proxy have a look at the server-side configure document.
Below are the most commony needed informations, every aspect of Docker and verdaccio is documented separately
To pull the latest pre-built docker image:
docker pull verdaccio/verdaccioSince version 2 images for every versions are availabel as tags.
To run the docker container:
docker run -it --rm --name verdaccio -p 4873:4873 verdaccio/verdaccio- Get the latest version of docker-compose.
- Build and run the container:
$ docker-compose up --buildDocker examples are available in this repository.
- Docker + Nginx
- Docker + Kubernetes
- Docker + Apache
A Verdaccio playbook is available at galaxy
Source: https://github.com/verdaccio/ansible-verdaccio
Maintainer: @030
The Verdaccio Chef cookbook is available via the chef supermarket.
Source: https://github.com/verdaccio/verdaccio-cookbook.
Maintainer: @kgrubb
Source: https://github.com/verdaccio/puppet-verdaccio.
Maintainer: No asigned yet
Verdaccio aims to support all features of a standard npm client that make sense to support in private repository. Unfortunately, it isn't always possible.
- Installing packages (npm install, npm upgrade, etc.) - supported
- Publishing packages (npm publish) - supported
- Unpublishing packages (npm unpublish) - supported
- Tagging (npm tag) - supported
- Deprecation (npm deprecate) - not supported
- Registering new users (npm adduser {newuser}) - supported
- Transferring ownership (npm owner add {user} {pkg}) - not supported, verdaccio uses its own acl management system
- Searching (npm search) - supported (cli / browser)
- Starring (npm star, npm unstar) - not supported, doesn't make sense in private registry
- Ping (npm ping) - supported
No CouchDB here. This application is supposed to work with zero configuration, so filesystem is used as a storage.
If you want to use a database instead, ask for it, we'll come up with some kind of a plugin system.
About the storage there is a running discussion here.
- npm + git (I mean, using git+ssh:// dependencies) - most people seem to use this, but it's a terrible idea... npm update doesn't work, can't use git subdirectories this way, etc.
- reggie - this looks very interesting indeed... I might borrow some code there.
- shadow-npm, public service - it uses the same code as npmjs.org + service is dead
- gemfury and others - those are closed-source cloud services, and I'm not in a mood to trust my private code to somebody (security through obscurity yeah!)
- npm-registry-proxy, npm-delegate, npm-proxy - those are just proxies...
- nexus-repository-oss - Repository manager that handles more than just NPM dependencies
- Is there something else?
- codebox-npm - Serverless private npm registry using
If you have any issue you can try the following options, do no desist to ask or check our issues database, perhaps someone has asked already what you are looking for.