Vercel CLI
Backend & InfraDevelop. Preview. Ship.
Release History
@vercel/connect@0.3.3vercel@56.2.0vercel@56.1.0@vercel/static-build@2.11.6@vercel/python@6.50.0@vercel/node@5.8.24@vercel/nestjs@0.2.104@vercel/koa@0.1.83@vercel/hono@0.2.103@vercel/h3@0.1.109@vercel/gatsby-plugin-vercel-builder@2.2.26@vercel/fs-detectors@6.13.0@vercel/fastify@0.1.103@vercel/express@0.1.114@vercel/elysia@0.1.100@vercel/client@17.6.5vercel@56.0.0@vercel/cervel@0.1.31@vercel/build-utils@13.33.0@vercel/backends@0.8.23@vercel/static-build@2.11.5@vercel/python@6.49.0@vercel/node@5.8.23@vercel/next@4.20.4@vercel/nestjs@0.2.103@vercel/koa@0.1.82@vercel/hono@0.2.102@vercel/h3@0.1.108@vercel/gatsby-plugin-vercel-builder@2.2.25@vercel/fs-detectors@6.12.1@vercel/frameworks@3.30.6@vercel/fastify@0.1.102@vercel/express@0.1.113@vercel/elysia@0.1.99@vercel/container@0.0.5@vercel/client@17.6.4vercel@55.0.0@vercel/cervel@0.1.30@vercel/build-utils@13.32.3@vercel/backends@0.8.22@vercel/fs-detectors@6.12.01 fixThis minor release primarily addresses a bug in service framework detection logic.
vercel@54.21.11 fix1 featureThis patch release introduces support for project-scoped flags across several commands and fixes an issue related to preserving generated service routes during build output merging.
@vercel/python@6.48.01 fixThis minor release primarily addresses a bug fix related to django services when handling static assets and vc dev environments.
@vercel/next@4.20.3This patch release updates the Next.js adapter to the latest version.
@vercel/fs-detectors@6.11.6This patch release primarily focused on updating internal dependencies.
@vercel/frameworks@3.30.55 featuresThis patch introduces an opt-in feature for framework detection during `vc build` on the first deployment, which records the detected framework and validates build output without slowing down the process.
vercel@54.21.05 fixes5 featuresThis release enables monorepo subdirectory build fixes by default, improving build context anchoring for linked projects. It also introduces opt-in framework detection during builds and updates several CLI commands for better agent output and dependency management.
vercel@54.20.12 fixesThis patch release updates the Vercel CLI by adding several missing commands to the root help output for better discoverability.
vercel@54.20.01 featureThis release introduces the `vercel agent-runs` command to enhance observability for Agent Runs, providing detailed inspection and tracing capabilities via the CLI.
@vercel/connect@0.3.23 featuresThis patch introduces the surfacing of the connector's human-readable name during authorization challenges and allows overriding this name via the `displayName` option in `connect()`.
vercel@54.19.01 fix1 featureThis release introduces new `vercel vcr` commands for managing Vercel Container Registry and improves route merging logic for nested Services V2 output. It also streamlines the acceptance of marketplace integration legal documents.
@vercel/rust@1.4.02 fixes1 featureThis release stabilizes the Rust runtime when running `vercel dev` by dynamically allocating ports, resolving intermittent startup failures. It also improves shutdown handling to ensure `waitUntil` background tasks complete during development.
@vercel/oidc-aws-credentials-provider@3.3.02 featuresThis release introduces in-memory caching for OIDC token exchanges to improve performance and adds an option to skip this cache. Dependencies were also updated.
@vercel/oidc@3.8.02 featuresThis release introduces in-memory caching for exchanged OIDC tokens to improve performance and adds an option to skip this new cache mechanism via `skipTokenCache` on `awsCredentialsProvider`.
@vercel/functions@3.7.5This patch release primarily focused on updating dependencies, specifically upgrading @vercel/oidc to version 3.8.0.
@vercel/connect@0.3.1This patch release primarily focused on updating dependencies, specifically bumping @vercel/oidc to version 3.8.0.
vercel@54.18.72 fixes1 featureThis patch introduces a fix for `vc build` in monorepo setups using in-place linking, ensuring correct root detection and dependency resolution. It also bridges WebSocket close events to response close.
@vercel/aws@0.2.7This patch release primarily focused on updating dependencies, specifically upgrading @vercel/oidc-aws-credentials-provider to version 3.3.0.
@vercel/express@0.1.112vercel@54.18.61 fixThis patch release updates dependencies and adjusts the rolling release start mechanism to use a dedicated API endpoint.
@vercel/cervel@0.1.29This patch release primarily focused on updating internal dependencies.
@vercel/backends@0.8.21BreakingThis patch introduces a build failure for services attempting to use the Edge Runtime, which is currently unsupported for services.
@vercel/fs-detectors@6.11.5This patch release primarily focused on updating dependencies, specifically @vercel/frameworks to version 3.30.4.
@vercel/frameworks@3.30.41 fixThis patch release updates the icon rendering for services and containers to correctly display circle icons in both dark and light modes.
vercel@54.18.51 featureThis patch release enhances the `vc logs` output by exposing the `cacheReason` field, providing users with more insight into cache behavior.
@vercel/passport@0.1.21 fixThis patch addresses an issue by ensuring the Passport cookie is read correctly from Vercel request context headers.
@vercel/fs-detectors@6.11.4This patch release primarily focused on updating internal dependencies.
@vercel/frameworks@3.30.3vercel@54.18.41 fix1 featureThis patch release fixes an issue with displaying rate-limit upgrade hints during deployment and corrects the command for purchasing v0 credits, while adding support for lazily generated Build Output services configs.
@vercel/next@4.20.21 featureThis patch introduces support for stable Cache Components, removing the dependency on experimental PPR.
@vercel/fs-detectors@6.11.31 fixThis patch release aligns service name validation across services and updates dependencies, including @vercel/frameworks to v3.30.2.
@vercel/frameworks@3.30.2This patch updates the Container framework logo to use the Box icon.
@vercel/container@0.0.46 fixes2 featuresThis patch primarily fixes several issues related to the `vercel dev` experience for the container framework, ensuring correct file detection, preventing build errors during dev, and improving container reuse and error reporting.
@vercel/connect@0.3.03 featuresThis release introduces adapter helpers under the @vercel/connect/chat subpath to simplify wiring Connect connectors for the Chat SDK, supporting both app-scoped tokens and webhook verification.
vercel@54.18.36 fixes2 featuresThis patch primarily fixes several issues related to running container builds in `vercel dev` mode, improving Docker daemon error reporting, and reusing the container dev server across requests. Dependencies were also updated.
@vercel/fs-detectors@6.11.21 fixThis patch release fixes an issue where bare static service builds were not resolving correctly, now allowing services defined only with 'root' to resolve via @vercel/static.
vercel@54.18.21 fixThis patch release fixes an issue where bare static service builds were not resolving correctly, now allowing services with only 'root' to resolve via @vercel/static.
@vercel/static-build@2.11.4This release contains only patch updates for @vercel/gatsby-plugin-vercel-builder to version 2.2.24.
@vercel/node@5.8.22This patch release primarily focused on updating internal dependencies, specifically @vercel/build-utils.
@vercel/nestjs@0.2.102@vercel/koa@0.1.81@vercel/hono@0.2.101@vercel/h3@0.1.107@vercel/gatsby-plugin-vercel-builder@2.2.24This patch release primarily involved updating dependencies, specifically @vercel/build-utils to version 13.32.2.
@vercel/fs-detectors@6.11.1This patch release primarily focused on updating internal dependencies, specifically @vercel/build-utils.
@vercel/fastify@0.1.101@vercel/express@0.1.111This patch release updates dependencies for @vercel/node to version 5.8.22 and @vercel/cervel to version 0.1.28.
@vercel/elysia@0.1.98@vercel/client@17.6.3This patch release primarily focused on updating internal dependencies, specifically @vercel/build-utils.
vercel@54.18.11 fix2 featuresThis patch fixes an issue where per-service function configurations were ignored during the build process for experimental V2 services. It also scopes derived queue consumer groups by service name to prevent path collisions.
@vercel/cervel@0.1.28@vercel/build-utils@13.32.21 fix2 featuresThis patch fixes an issue where per-service function configurations were ignored during the build process for experimental V2 services. Consumer groups for queue/v2beta are now correctly scoped by service name to prevent collisions.
@vercel/backends@0.8.20This patch release primarily focused on updating internal dependencies, specifically @vercel/build-utils.
@vercel/python-runtime@0.16.01 featureThis release introduces WebSocket support for WSGI applications, allowing platforms to handle bidirectional streaming after the initial handshake.
@vercel/python@6.47.31 fixThis patch simplifies the runtime output structure for isolated services by changing the function emission location.
@vercel/oidc-aws-credentials-provider@3.2.1This patch release primarily consists of dependency updates, specifically updating @vercel/oidc to version 3.7.1.
@vercel/oidc@3.7.1This patch introduces a deprecation for the synchronous Vercel OIDC token retrieval function, encouraging the use of its asynchronous counterpart.
@vercel/go@3.10.21 fixThis patch simplifies the runtime output structure for isolated services by changing the function emission location.
@vercel/functions@3.7.4This patch release primarily focused on updating dependencies, specifically upgrading @vercel/oidc to version 3.7.1.
@vercel/fs-detectors@6.11.0Breaking3 fixes4 featuresThis release migrates service auto-detection to the V2 format and significantly refines container detection logic, removing support for implicit OCI image reference entrypoints.
Common Errors
ModuleNotFoundError6 reportsThe "ModuleNotFoundError" in vercel-cli CI typically arises from missing dependencies not installed during the build process. To fix, ensure that your `package.json` accurately lists all required dependencies, and that your build process includes a `npm install` or `yarn install` step before running vercel-cli commands. Double-check that any optional dependencies crucial for CI/CD are also installed.
FetchError2 reportsFetchError in vercel-cli usually indicates network connectivity problems preventing the tool from reaching Vercel's API. To resolve it, ensure your machine has stable internet access and that no firewall or proxy settings are blocking outbound requests to `api.vercel.com`. You might also try updating vercel-cli to the latest version as newer versions often include improved error handling and retry mechanisms.
Related Backend & Infra Packages
Production-Grade Container Scheduling and Management
Node.js JavaScript runtime ✨🐢🚀✨
Promise based HTTP client for the browser and node.js
A modern runtime for JavaScript and TypeScript.
Deliver web apps with confidence 🚀
Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
Subscribe to Updates
Get notified when new versions are released