Packages

@vercel/build-utils

15.5.0 · 18 Nov 2026Apache-2.07.9M / weekRepositoryHomepagenpmAtom feed

Your version

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

  1. 14.x
  2. 14.0.3

    8 Aug 2026

    Maintenance only: docs, tests, build or refactoring. Nothing changes in how you use it.

  3. 14.0.2

    7 Aug 2026
    • Scope the pre-compilation install's VERCEL_INSTALL_COMPLETED marker to the package.json it installed. Previously, a vercel.toml/vercel.ts config caused vc build to install at the repo root and then silently skip every later default install, so services whose install root is a different workspace (its own package.json/lockfile) built without dependencies.

  4. 14.0.1

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

  5. 13.x
  6. 13.36.3

    30 Jul 2026
    • Propagate per-function maxConcurrency configuration into build outputs and keep every configured Next.js route in its own Lambda group, including routes with the same limit.

    • Type shared function settings in container image build outputs.

  7. 13.36.2

    29 Jul 2026
    • Preserve 4-byte UTF-8 characters when streaming string FileBlob contents (fixes Edge Function corruption during vercel build).

  8. 13.36.1

    29 Jul 2026
    • Replace the vercel-workers integration for Python queue subscribers and workflows with the new vercel-queue SDK:

  9. 13.36.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.

  10. 13.35.0

    24 Jul 2026
    • Make service bindings type optional.

  11. 13.34.0

    16 Jul 2026
    • Support Python services that declare their web app and development workflow sidecars through a pyproject.toml entrypoint in vercel dev.

  12. 13.33.1

    15 Jul 2026
    • 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.

  13. 13.33.0

    13 Jul 2026
    • Add service information to deploy-manifest.

  14. 13.32.3

    9 Jul 2026
    • Add vercel dev support for Python queue subscribers defined in pyproject.toml.

  15. 13.32.2

    27 Jun 2026
    • Apply per-service functions config when building experimental V2 services. Previously, function configuration declared under services.<name>.functions in vercel.json (experimentalTriggers, maxDuration, memory, architecture, regions, functionFailoverRegions, supportsCancellation) was dropped at build time — only the top-level functions map was honored. The build now feeds each service's functions to its lambdas for both single-lambda builders (@vercel/node, etc., via writeBuildResultV3) and framework builders that read config.functions (e.g. @vercel/next, via the builder config). Derived queue/v2beta consumer groups are now scoped by the owning service name so two services that declare the same function path + topic no longer collide.

  16. 13.32.1

    24 Jun 2026
    • Fix vercel dev for standalone Node servers, including projects without a package.json, and reuse the server process between requests.

  17. 13.32.0

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

    • Add an experimental container service runtime. A service with
      runtime: "container" either builds its Dockerfile/Containerfile and pushes
      the resulting OCI image to the Vercel Container Registry (VCR), or passes a
      prebuilt image reference through as build output.

      Buildah specifics in the build container: host networking for RUN steps,
      native overlay storage on the XFS /vercel volume (deferring to the image's
      storage.conf), zstd push compression, and registry credentials read from the
      provisioned auth file when present. Several knobs are available for debugging:
      VERCEL_CONTAINER_ENGINE, VERCEL_VCR_STRICT_STORAGE,
      VERCEL_VCR_DISABLE_LAYER_CACHE, and VERCEL_VCR_FORCE_LOGIN.

    • Set the Node.js 20 discontinuation date to October 1, 2026.

  18. 13.31.1

    23 Jun 2026
    • Add support to experimentalServicesV2 for bindings in vc dev

  19. 13.31.0

    23 Jun 2026
    • Add deploy-manifest as an extension of project manifest.

    • Emit project manifest for hugo, zola, jekyll, and middleman frameworks.

    • Autodetect Bun runtime if engines.bun is set.

  20. 13.30.0

    11 Jun 2026
    • Add hasFallback, htmlSize, and isDynamicRoute to Prerender

      These optional fields surface per-route PPR shell metadata in the Build Output so consumers can classify prerenders (e.g. full shell vs. empty shell vs. concrete prerender):

  21. 13.29.1

    11 Jun 2026
    • Elevate maximum maxDuration to 1800s

  22. 13.29.0

    10 Jun 2026
    • Evaluate the maxDuration upper bound at validation time so VERCEL_CLI_SKIP_MAX_DURATION_LIMIT works regardless of import order.

      The gate was read when @vercel/build-utils' functionsSchema was constructed and when the CLI compiled its vercel.json validator — both at module load. Any process that imports these modules before setting the env var baked in the default 900-second maximum and ignored the flag, failing with Invalid vercel.json - functions[...].maxDuration should be <= 900.

      @vercel/build-utils now exposes getFunctionsSchema(), which reads the limit at call time (the existing functionsSchema const is kept but deprecated). The CLI builds and compiles its config validator lazily, caching one validator per resolved limit, so setting the variable after import takes effect. Default behavior is unchanged — the 900s maximum, the lower bound, and the integer check are all still enforced when the variable is unset.

  23. 13.28.0

    8 Jun 2026
    • Add a per-route hasPostponed signal to Prerender.

      @vercel/build-utils exposes a new optional hasPostponed?: boolean field on Prerender / PrerenderOptions. It is a tri-state: true when the route's .meta postponed state is present (React suspended during the build-time prerender), false when the framework prerendered a Prerender route without postponing, and undefined when the framework did not provide the signal.

      @vercel/next populates it for app-router PPR routes (computed from the route's postponed state) and leaves it undefined for pages-router and other non-app-router prerenders. This is an additive, finer-grained signal — it does not change the existing chain / experimentalStreamingLambdaPath behavior — so downstream consumers can distinguish a route that actually postponed from one that has PPR machinery but fully prerendered (e.g. under cacheComponents: true).

  24. 13.27.2

    8 Jun 2026
    • Gate the client-side 900-second maxDuration upper bound behind the VERCEL_CLI_SKIP_MAX_DURATION_LIMIT environment variable. The limit is now owned by a single helper in @vercel/build-utils instead of being hardcoded in multiple validators. When the variable is set to 1, the client-side maximum is skipped and validation defers to the server. Default behavior is unchanged — the maximum, the lower bound, and the integer check are all still enforced when the variable is unset.

    • Fix Node.js API entrypoint detection dropping functions whose source contains comment-like sequences (/*, //, */) inside string, template, or regex literals — for example an Accept: */* header. Handler exports are now identified with the ES/CJS module lexers instead of stripping comments with regexes, so the contents of literals are never mistaken for comments.

  25. 13.27.1

    4 Jun 2026
    • Wire experimentalServicesV2 into fs-detectors.

  26. 13.27.0

    3 Jun 2026
    • Add isPackageInstalled util for detecting dependencies during build.
      Fix Vercel Flags dependency detection for emitting datafiles during builds with OIDC tokens.

  27. 13.26.6

    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.

  28. 13.26.5

    1 Jun 2026
    • Revert "[flags] fix dep detection for build embedding (#16242)"

  29. 13.26.4

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

  30. 13.26.3

    27 May 2026
    • Fix prebuilt deployments failing with "invalid relative path" when using the --standalone flag in pnpm monorepos by skipping external node_modules symlinks and copying traced files at their logical paths instead.

  31. 13.26.2

    26 May 2026
    • Cleanup getLambdaSupportsStreaming

  32. 13.26.1

    22 May 2026
    • Fix config.framework in deserializeBuildOutput

    • Support workflow-triggered job services in queue infrastructure

      Add isWorkflowTriggeredService() and isQueueBackedService() helpers so workflow services
      are recognized by the queue broker, dev server, and build pipeline. Update Python runtime to
      bootstrap workflow services as queue-backed workers.

  33. 13.26.0

    19 May 2026
    • Allow builder V2 to expose startDevServer.

    • Include framework slug in output/config.json

  34. 13.25.0

    15 May 2026
    • Add normalized entrypoint detector for runtime builders.

    • Add preDeployCommand for experimentalServices

  35. 13.24.0

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

  36. 13.23.0

    11 May 2026
    • Add project manifest to node builder.

    • services schema support

  37. 13.22.1

    10 May 2026
    • Disable response streaming for lambdas with awsLambdaHandler set inside getLambdaSupportsStreaming. This closes a gap where non-Node builders (e.g. @vercel/redwood) constructed NodejsLambda with awsLambdaHandler but no explicit supportsResponseStreaming, causing finalizeLambda to silently flip streaming on for AWS custom handlers. With the gate now enforced centrally in finalizeLambda, the equivalent @vercel/node build-time check from #16266 is consolidated away — all builders go through the same gate.

  38. 13.22.0

    9 May 2026
    • Add service type to project manifest.

  39. 13.21.0

    30 Apr 2026
    • Upgrade to TypeScript 5.9

  40. 13.20.0

    22 Apr 2026
    • Add framework to package manifest for python and backends builders.

    • Add shared build output deserialization helpers for existing callers.

  41. 13.19.1

    20 Apr 2026
    • Simplify streaming lambda check

  42. 13.19.0

    17 Apr 2026
    • Move Python workers to v2beta triggers with private routing

    • Added a shared build result validation helper in @vercel/build-utils for existing callers.

  43. 13.18.0

    17 Apr 2026
    • Generate PROJECTMANIFEST in @vercel/backends for Node deployments.

  44. 13.17.1

    16 Apr 2026
    • Align deserialize logic with existing callers.

  45. 13.17.0

    15 Apr 2026
    • Support dynamically specifying crons from a python service

  46. 13.16.0

    15 Apr 2026
    • Add shared deserialization and build-result collection utilities.

    • Add root to experimentalServices to set a service's working directory.

    • Add a new flag to vercel deploy to let users deploy to hive

  47. 13.15.0

    14 Apr 2026
    • Allow multiple v2beta triggers for a single Lambda when config is coming from services

    • Add deserialization utilities

  48. 13.14.2

    11 Apr 2026
    • Add mount support for experimental services across config validation and service resolution.

  49. 13.14.1

    10 Apr 2026
    • Restore finalizeLambda() to return zipPath: null for the default in-memory path, preserving the existing caller-facing result contract while keeping custom ZIP strategies supported.

    • node: Filter non-entrypoint Node.js files in /api directory

  50. 13.14.0

    8 Apr 2026
    • Support configuration via vercel.toml

  51. 13.13.0

    7 Apr 2026
    • Extend finalizeLambda with pluggable ZIP strategy (createZip), pre-digest validation hook (validateZip), and optional trace tags. Widen getLambdaEnvironment buffer param to { byteLength: number }.

  52. 13.12.2

    1 Apr 2026
    • Extract finalize/validate function utils for build-utils

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.