Skip to main content

v0 now reads npm credentials from shared environment variables

By Steven Van ·

v0 installs private npm packages using NPM_TOKEN or NPM_RC set as shared environment variables on Vercel.

v0 can now install private npm packages using credentials stored as shared environment variables on Vercel, making it easier to build with a team's existing design systems, component libraries, and internal packages directly in v0.

  • Add NPM_TOKEN for private packages hosted on registry.npmjs.org, scoped to Development and/or Preview.
  • Add NPM_RC to configure custom or multiple registries, including scoped registries (such as an organization scope like @acme) and references to other environment variables, for setups like GitHub Packages or a private JFrog Artifactory registry.
  • Credentials can be marked sensitive; v0 never exposes them to the model or writes them to the sandbox filesystem.

Integration status is visible from Settings → Integrations in v0. Full details are in the announcement.

Vercel
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →

Read the original announcement →

Read v0 now reads npm credentials from shared environment variables on Creators Toolbox