Packages

@vercel/client

18.12.4 · 18 Nov 2026Apache-2.0119.5k / weekRepositoryHomepagenpmAtom feed

Your version

396 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 18.x · latest line
  2. 18.2.10

    13 Aug 2026
    • Root-anchor the prebuilt deploy ignore negations so files under .vercel other than .vercel/output are not accidentally re-included when a positive .vercel pattern was compiled earlier in the same process (e.g. an in-process vercel build).

  3. 18.2.9

    11 Aug 2026
    • Remove redundant and ineffective package tests.

  4. 18.2.6 – 18.2.83 releases that only update dependencies@vercel/build-utils 14.0.4Show each
  5. 18.2.5

    3 Aug 2026
    • Bump all workspace packages to trigger a full publish from vercel-internal.

  6. 18.2.3

    30 Jul 2026
    • Fix vercel deploy --prebuilt re-adding .vercelignored files through filePathMap. Source paths referenced by .vc-config.json filePathMap entries are now re-checked against the project's .vercelignore/.nowignore rules and rejected when they resolve outside the deployment root, so a tampered or lower-trust build artifact can no longer reintroduce ignored files (e.g. .env) into the deployment upload set.

  7. 18.2.1 – 18.2.22 releases that only update dependencies@vercel/build-utils 13.36.2Show each
  8. 18.2.0

    27 Jul 2026
    • Support Node.js Routing Middleware entrypoints through proxy.entrypoint, with optional path matching through proxy.matcher. The matcher may be configured in the entrypoint source or vercel.json, but not both.

  9. 18.1.1

    24 Jul 2026

    Only updates a dependency:@vercel/build-utils 13.35.0

  10. 18.1.0

    16 Jul 2026
    • Skip the Rust target/ directory by default for Rust projects.

      Rust projects produce a target/ directory of build artifacts that can be
      hundreds of MB. It's rebuilt on Vercel during the deployment (and cached
      server-side), so uploading it only slows deployments down. When a root
      Cargo.toml is detected, target/ is now ignored by default during
      vercel deploy and vercel dev. Users can opt back in with !/target in
      their .vercelignore.

      Also hardened the local file scanner used by vercel dev so that a directory
      removed mid-scan (a common race with cargo build churning target/) is
      skipped instead of crashing the process.

  11. 18.0.0

    15 Jul 2026
    • Breaking

      Migrate @vercel/client and @vercel/build-utils from node-fetch to native fetch. This removes the last url.parse() usage from the CLI bundle, which triggered a DEP0169 DeprecationWarning on Node 24 (visible in the standalone binary during vercel deploy).

      BREAKING CHANGE (@vercel/client): the agent?: http.Agent option was replaced with dispatcher?: FetchDispatcher (an undici dispatcher, e.g. undici.ProxyAgent), since native fetch does not support Node.js HTTP agents. The CLI now threads its proxy-aware dispatcher through automatically, so HTTP_PROXY/HTTPS_PROXY behavior is unchanged for CLI users.

  12. 17.x
  13. 17.6.5

    13 Jul 2026

    Only updates a dependency:@vercel/build-utils 13.33.0

  14. 17.6.4

    9 Jul 2026
    • Finish CLI deployments from alias-assigned build stream events while retaining deployment polling as a fallback.

  15. 17.6.3

    27 Jun 2026

    Only updates a dependency:@vercel/build-utils 13.32.2

  16. 17.6.2

    25 Jun 2026
    • Handle deployments containing very large files without crashing. Files larger than Node's fs.readFile limit (~2 GiB) are now hashed and uploaded by streaming instead of being read into a single Buffer (which threw ERR_FS_FILE_TOO_LARGE — "File size ... is greater than 2 GiB"), and the CLI upload progress no longer assumes every file is held in memory. When a file still exceeds the server's per-request upload limit (HTTP 413), the CLI now suggests --archive=tgz, which uploads the deployment in smaller chunks.

  17. 17.6.1

    24 Jun 2026
    • Add vercel deploy --dry to inspect the detected framework preset and local deployment file set without uploading or creating a deployment, with complete JSON output for non-TTY consumers.

  18. 17.6.0

    24 Jun 2026
    • Add services as the canonical multi-service project configuration and keep experimentalServicesV2 as a deprecated backwards-compatible alias.

  19. 17.5.9 – 17.5.1810 releases with no change for you9 dependency updates, 1 maintenance@vercel/build-utils 13.31.1@vercel/routing-utils 6.3.1Show each
  20. 17.5.8

    3 Jun 2026
    • Remove the services field from vercel.json and the VERCEL_USE_SERVICES gate.

    • Add experimentalServicesV2 field to vercel.json implementing the new schema for services.

  21. 17.5.7

    1 Jun 2026

    Only updates a dependency:@vercel/build-utils 13.26.5

  22. 17.5.6

    28 May 2026
    • Drop top-level env support for the new service-ref shape for services.

  23. 17.5.1 – 17.5.55 releases that only update dependencies@vercel/build-utils 13.26.3Show each
  24. 17.5.0

    13 May 2026
    • Add support for env vars injection that reference other services in services with an explicit env configuration.

  25. 17.4.3

    11 May 2026
    • services schema support

  26. 17.4.1 – 17.4.22 releases that only update dependencies@vercel/build-utils 13.22.1Show each
  27. 17.4.0

    30 Apr 2026
    • Upgrade to TypeScript 5.9

  28. 17.3.3 – 17.3.107 releases that only update dependencies@vercel/build-utils 13.20.0Show each

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.