Vercel
Shared environment variable support now lets v0 install private npm packages. Teams can use their existing design systems, component libraries and internal packages while building an app.
According to the Vercel changelog, the credentials come from shared environment variables on Vercel. They can be scoped to Development, Preview or both.
This covers packages hosted on the main npm registry as well as custom registries. The latter includes services such as GitHub Packages and JFrog Artifactory.
v0 Supports NPM_TOKEN and NPM_RC
There are two configuration routes, depending on where the private packages live.
| Variable | Use it for | Registry support |
|---|---|---|
NPM_TOKEN | Authenticating private npm packages | registry.npmjs.org |
NPM_RC | Configuring custom or multiple registries | Scoped registries, GitHub Packages and JFrog Artifactory |
NPM_RC can reference other environment variables. A team could configure an organisation scope such as @acme for GitHub Packages, or direct private package requests through a JFrog Artifactory registry.
Once the variable is added, v0 reads the credentials when it needs to install a package. The integration status appears under Settings → Integrations, giving teams a place to check that the connection is active.
Shared npm Credentials Stay Outside the Model
Credentials can be marked as sensitive in Vercel. v0 does not expose those credentials to the model or write them to disk.
That separation allows the generated app to install authorised packages without placing the registry token inside a prompt or generated project file. Teams can therefore bring private UI components and internal packages into the same v0 workflow used for public dependencies.
Frequently asked questions
What is Vercel shared npm credential support in v0?
It lets v0 install private npm packages using credentials stored as shared environment variables. It supports the main npm registry and custom registries, including scoped registries.
How do I connect a private npm package to v0?
Add NPM_TOKEN as a shared environment variable for packages on registry.npmjs.org. Use NPM_RC for custom or multiple registries, then scope the variable to Development, Preview or both.
Which Vercel plan includes private npm packages in v0?
The changelog does not list pricing or plan requirements. It says the credentials are configured through Vercel shared environment variables.
Sources
3 checkedHow we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.
n8n