verdaccio
A lightweight private Node.js proxy registry
Contribute
Become a financial contributor.
Financial Contributions
Events
verdaccio is hosting the following events.
Top financial contributors
Organizations
$8,000 USD since Oct 2019
$1,200 USD since Jun 2022
$1,082.7 USD since Nov 2020
$580 USD since Nov 2020
$500 USD since Jun 2018
$485.55 USD since Jun 2019
$250 USD since Jun 2020
$177 USD since Dec 2019
$150 USD since Oct 2020
$150 USD since Oct 2020
Individuals
$198 USD since Nov 2018
$157 USD since May 2018
$75 USD since May 2019
$50 USD since Feb 2019
$50 USD since Aug 2019
$50 USD since Aug 2021
$36 USD since Jul 2019
$27 USD since Jun 2020
$25 USD since Jul 2019
$25 USD since May 2021
verdaccio is all of us
Our contributors 50
Thank you for supporting verdaccio.
Ayush Sharma
$10 USD
Sergio Herrer...
Priscila Oliv...
Daniel Ruf
GatsbyJS
$8,000 USD
PQINA
$1,200 USD
GitHub Sponsors
$1,083 USD
Sterfive - Op...
$580 USD
Budget
Transparent and open finances.
Credit from Third Iron to verdaccio •
Credit from Kyle Smith to verdaccio •
$5,787.67 USD
$11,800.50 USD
$6,012.83 USD
$543.67 USD
Connect
Let’s get the ball rolling!
News from verdaccio
Updates on our activities and progress.
Node.TLV 2022 video and more updates
Verdaccio at NodeTLV an some updates
Verdaccio at Global Summit for NODE JS 2022
Conversations
Let’s get the discussion going! This is a space for the community to converse, ask questions, say thank you, and get things done together.
If you like 😍 Verdaccio, feel free to drop your thoughts here 🥰
Published on January 21, 2020 by Juan Carlos Picado
:)
About
Verdaccio is a simple, zero-config-required local private npm registry. No need for an entire database just to get started! Verdaccio comes out of the box with its own tiny database, and the ability to proxy other registries (eg. npmjs.org), caching the downloaded modules along the way. For those looking to extend their storage capabilities, Verdaccio supports various community-made plugins to hook into services such as Amazon's s3 and Google Cloud Storage.
Use private packages
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.
Cache npmjs.org registry
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, Many packages suddenly disappeared or Registry returns 404 for a package I have installed before.
Link multiple registries
If you use multiples registries in your organization and need to fetch packages from multiple sources in one single project you might take advance of the uplinks feature with Verdaccio, chaining multiple registries and fetching from one single endpoint.
Override public packages
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.