Vercel Agent now installs private packages from npm and custom registries
Vercel Agent can now install private dependencies from npm and custom registries using team-shared environment variables. Credentials are securely stored outside the sandbox, and npm, pnpm, and classic Yarn authenticate the same way as in Vercel builds.
Vercel Agent can install private dependencies from npm and custom registries using credentials stored as shared environment variables on Vercel. , , and classic Yarn running in Agent sessions authenticate as they do in Vercel builds.npmpnpm
To get started, add a for Development or Preview:shared environment variable
Vercel Agent reads only team-shared variables, not project-scoped ones. Credential values stay outside the sandbox, so the agent cannot read them.
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 ↗
More from Vercel
Follow Vercel to get its new changes in your feed and email digest.
Agents can now buy domains with the Vercel CLI
Vercel CLI now enables agents to discover, check availability, and initiate domain purchases through structured commands, with purchase confirmation remaining under user control via interactive terminal or dashboard approval.
New Pro teams default to 30-day deployment retention
Pro teams now default to a 30-day deployment retention period to balance keeping recent history available while reducing storage costs. You can configure a longer retention period in team settings if needed.
Deployment Storage billing begins for existing Pro teams
Pro teams will now be charged for Deployment Storage and Functions Storage at $0.10 per GB-month. The default deployment retention window changes to 30 days, with deployments older than 30 days deleted automatically unless you adjust your retention settings beforehand.