Where Does Verdaccio Store Config and Packages?
Verdaccio resolves config.yaml through XDG paths and keeps published tarballs under the data home storage dir.
Last updated
Verdaccio picks its config by searching candidates in order: $XDG_CONFIG_HOME/verdaccio/config.yaml on Linux and Mac, %APPDATA%\verdaccio\config.yaml on Windows, then ./verdaccio/config.yaml and ./config.yaml beside the launch directory. First file found wins, so a stray local copy silently beats the global one.
Published tarballs default to ~/.local/share/verdaccio/storage with the .verdaccio-db database inside, separate from the config tree. Back up both. Unsure which file is live? verdaccio --info prints the active config path and the startup log names its choice.
Where Verdaccio stores this, by platform
~/.config/verdaccio/config.yaml + ~/.local/share/verdaccio/storage
Config under XDG_CONFIG_HOME, storage under XDG_DATA_HOME. Override with --config, VERDACCIO_STORAGE_PATH, or systemd unit paths /etc/verdaccio/config.yaml and /var/lib/verdaccio. Back up storage plus config together.
%APPDATA%\verdaccio\config.yaml
Same candidate search as Linux, so a config.yaml in the launch folder shadows this one. Run verdaccio --info when settings seem ignored. Storage defaults under the local data home unless the config sets its own path.
~/.config/verdaccio/config.yaml
Same XDG style path as Linux, not Application Support. Docker images use /verdaccio/storage and /opt/verdaccio instead, so container data lives in volumes, not these paths.
Frequently asked questions
Verdaccio ignores my config changes. Why?
It is reading a different file. The candidate search prefers ./config.yaml in the launch directory over the global one. Run verdaccio --info to print the active path, or check the conf field of the /-/_debug endpoint.
How do I back up a Verdaccio registry?
Copy config.yaml with htpasswd plus the entire storage directory including .verdaccio-db.json. That trio restores users, rules, and every published version. Uplink cached tarballs live there too.
Notice an outdated path? Let us know.