# v0 now reads npm credentials from shared environment variables

Publisher-attributed story with a reviewed brief or permitted publisher paragraph. The original publisher is responsible for the linked reporting.

- Publisher: Vercel
- Author credit: Vishal Yathish; Sahaj Jain
- Category: Cloud
- Original publication time: 2026-09-18T17:00:00Z
- Original update time: 2026-09-18T17:00:00Z
- First observed by NexusTechWire: 2026-10-01T20:28:47Z
- Original source: https://vercel.com/changelog/v0-now-reads-npm-credentials-from-shared-environment-variables
- NexusTechWire record: https://nexustechwire.com/news/news-8a23fcddbac459b0da0b

## The brief

v0 can now install private npm or custom-registry packages using shared Vercel environment variables scoped to Development or Preview. Teams can supply NPM\_TOKEN for npm's registry or NPM\_RC for custom and multiple registries, bringing internal libraries into their builds. Vercel says these credentials are neither shown to the model nor written to the sandbox filesystem; integration status appears in v0 settings.

AI-assisted NexusTechWire summary, checked against the linked source on 2026-10-02T00:20:18Z. Not independent reporting.

Read the full original: [Vercel](https://vercel.com/changelog/v0-now-reads-npm-credentials-from-shared-environment-variables)

This record does not reproduce the complete article or represent independent confirmation of every source claim.