v0 now reads npm credentials from shared environment variables
v0 now installs private packages from npm and custom registries using credentials stored as shared environment variables on Vercel, making it easier for teams to build with their existing design systems and internal packages directly in v0.
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 following as a on Vercel, scoped to Development and/or Preview:shared environment variable
supports scoped registries and references to other environment variables. For example, configure an organization scope such as for GitHub Packages, or direct package requests through a private JFrog Artifactory registry.NPM_RC@acme
Credentials can be marked sensitive, and v0 never exposes them to the model or writes them to the sandbox filesystem.
You can view the integration status from in v0.Settings → Integrations
Learn more in the .private dependencies docs
Use for private packages hosted on .
NPM_TOKENregistry.npmjs.orgUse to configure custom or multiple registries.
NPM_RC
Source: original entry ↗