v0 now reads npm credentials from shared environment variables

Vercel’s v0 AI coding assistant now reads npm credentials from shared environment variables configured in Vercel projects. This change allows teams to install private packages hosted on npm or custom registries without additional setup. The feature targets development and preview environments, ensuring credentials remain accessible only where needed. Teams can reuse existing design systems and internal packages seamlessly within v0.

To use the feature, developers must add either NPM_TOKEN or NPM_RC as a shared environment variable in Vercel. NPM_TOKEN is intended for private packages on registry.npmjs.org, while NPM_RC supports custom or multiple registries. The NPM_RC variable can reference other environment variables, enabling flexible registry configurations. This approach simplifies access to scoped registries like GitHub Packages or private registries such as JFrog Artifactory.

Credentials added as environment variables can be marked as sensitive, preventing exposure to the v0 model or sandbox filesystem. This ensures security while maintaining functionality. The integration status can be verified through the Settings → Integrations section in v0. Developers retain control over where and how credentials are used.

The update eliminates the need for manual credential entry in each project, streamlining the workflow for teams using private packages. By centralizing credentials in Vercel’s environment variables, v0 reduces setup complexity and improves consistency across projects. This change aligns with Vercel’s focus on simplifying development workflows for teams.