AI Briefing
KO

v0 Supports Private npm Package Installation via Vercel Shared Environment Variables

·2026.09.18 09:00

Key point

v0 now supports installing private npm packages and custom registries through Vercel's shared environment variables.

Details

v0 now allows installing packages from npm private packages and custom registries by leveraging Vercel's shared environment variables. This enables teams to directly utilize existing design systems, component libraries, and internal packages within v0 for development.

Setup

Add one of the following shared environment variables in Vercel for the Development or Preview scope:

  • NPM_TOKEN: For private packages hosted on registry.npmjs.org
  • NPM_RC: For custom or multiple registry configurations

NPM_RC supports scoped registries and references to other environment variables. For example, you can configure the @acme organization scope for GitHub Packages or route requests to a private registry like JFrog Artifactory.

Security and Verification

Credentials can be marked as sensitive, and v0 does not expose them to the model or write them to the sandbox file system. Connection status can be checked in v0's Settings → Integrations.

This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.

Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.