v0 now reads npm credentials from shared environment variables
v0 now pulls private npm packages into its design-to-code pipeline — teams can build with their own component libraries without manual credential juggling.
Why it matters
v0 (Vercel's AI code-generation tool) adds support for private npm registries via shared environment variables, lowering friction for teams using internal design systems and component libraries in AI-assisted development workflows.
The key facts
11 to knowv0 can now authenticate to private npm registries using NPM_TOKEN and NPM_RC environment variables
Supports scoped registries (@acme), GitHub Packages, and custom registries like JFrog Artifactory
Credentials marked as sensitive and never exposed to the model or sandbox filesystem
Integration status viewable in v0 Settings → Integrations
Feature scoped to Development and/or Preview environments on Vercel
v0 now supports private npm package installation via shared environment variables on Vercel
Supports scoped registries (@acme) and custom registries (JFrog Artifactory, GitHub Packages)
Credentials marked as sensitive; not exposed to model or written to sandbox filesystem
Integration status visible in v0 Settings → Integrations
Works with NPM_TOKEN and NPM_RC environment variable patterns
Scoped to Development and/or Preview environments
Go to the source
Vercel Blogvercel.com
Publisher excerpt: now installs private packages from npm and custom registries using credentials stored as shared environment variables on Vercel.v0 This makes it easier for teams to build with their existing design systems, component libraries, and internal packages directly in v0. To get started, add one of the…