Works with npm clients
Use normal registry configuration and auth tokens for npm, Yarn, pnpm, and Bun installs across Node.js services, JavaScript libraries, TypeScript packages, and WebAssembly modules.
Ravenstash hosts scoped and unscoped npm packages for Node, Node.js, JavaScript, TypeScript, and WebAssembly teams that want private package delivery without a separate registry workflow.
npm config set @acme:registry https://rvnsta.sh/npm/x/acme/frontend/
npm config set //rvnsta.sh/npm/x/acme/frontend/:_authToken "${RAVENSTASH_TOKEN}"
npm install @acme/design-systemnpm publish \
--registry https://push.rvnsta.sh/native/npm/x/acme/frontendRavenstash is built to make private package publishing feel familiar for developers and manageable for teams.
Use normal registry configuration and auth tokens for npm, Yarn, pnpm, and Bun installs across Node.js services, JavaScript libraries, TypeScript packages, and WebAssembly modules.
Serve private npm packages and tarballs through authenticated Ravenstash routes built for developer machines and CI.
Let approved npmjs.org packages flow through your private registry and keep repeat installs faster from the Ravenstash cache.
These examples use placeholder customer and repository names. Replace them with your Ravenstash customer and repository public IDs.
npm config set @acme:registry https://rvnsta.sh/npm/x/acme/frontend/
npm config set //rvnsta.sh/npm/x/acme/frontend/:_authToken "${RAVENSTASH_TOKEN}"
npm install @acme/design-systemnpm publish \
--registry https://push.rvnsta.sh/native/npm/x/acme/frontend@acme:registry=https://rvnsta.sh/npm/x/acme/frontend/
//rvnsta.sh/npm/x/acme/frontend/:_authToken=${RAVENSTASH_TOKEN}Yes. Ravenstash supports the npm package data and tarball downloads that standard npm clients expect.
Full npm dist-tag management is coming later. Today, standard installs resolve the latest published version from the package history.
Yes. npm repositories can fall back to approved upstream packages and cache them for future installs.