@vercel/build-utils
15.5.0 · 18 Nov 2026Apache-2.07.9M / weekRepositoryHomepagenpmAtom feed
345 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 14.x
14.0.3
8 Aug 2026Maintenance only: docs, tests, build or refactoring. Nothing changes in how you use it.
14.0.2
7 Aug 2026Scope the pre-compilation install's
VERCEL_INSTALL_COMPLETEDmarker to thepackage.jsonit installed. Previously, avercel.toml/vercel.tsconfig causedvc buildto install at the repo root and then silently skip every later default install, so services whose install root is a different workspace (its ownpackage.json/lockfile) built without dependencies.
14.0.1
3 Aug 2026Bump all workspace packages to trigger a full publish from vercel-internal.
Patch Changes
Bump all workspace packages to trigger a full publish from vercel-internal.
- 13.x
13.36.3
30 Jul 2026Propagate per-function
maxConcurrencyconfiguration 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.
13.36.2
29 Jul 2026Preserve 4-byte UTF-8 characters when streaming string
FileBlobcontents (fixes Edge Function corruption duringvercel build).
13.36.1
29 Jul 2026Replace the vercel-workers integration for Python queue subscribers and workflows with the new vercel-queue SDK:
13.36.0
27 Jul 2026Support Node.js Routing Middleware entrypoints through
proxy.entrypoint, with optional path matching throughproxy.matcher. The matcher may be configured in the entrypoint source orvercel.json, but not both.
Minor Changes
Support Node.js Routing Middleware entrypoints through
proxy.entrypoint, with optional path matching throughproxy.matcher. The matcher may be configured in the entrypoint source orvercel.json, but not both.
13.35.0
24 Jul 2026Make service bindings type optional.
13.34.0
16 Jul 2026Support Python services that declare their web app and development workflow sidecars through a
pyproject.tomlentrypoint invercel dev.
13.33.1
15 Jul 2026Migrate
@vercel/clientand@vercel/build-utilsfromnode-fetchto nativefetch. This removes the lasturl.parse()usage from the CLI bundle, which triggered aDEP0169DeprecationWarning on Node 24 (visible in the standalone binary duringvercel deploy).BREAKING CHANGE (
@vercel/client): theagent?: http.Agentoption was replaced withdispatcher?: FetchDispatcher(an undici dispatcher, e.g.undici.ProxyAgent), since nativefetchdoes not support Node.js HTTP agents. The CLI now threads its proxy-aware dispatcher through automatically, soHTTP_PROXY/HTTPS_PROXYbehavior is unchanged for CLI users.
13.33.0
13 Jul 2026Add service information to deploy-manifest.
13.32.3
9 Jul 2026Add
vercel devsupport for Python queue subscribers defined inpyproject.toml.
13.32.2
27 Jun 2026Apply per-service
functionsconfig when building experimental V2 services. Previously, function configuration declared underservices.<name>.functionsinvercel.json(experimentalTriggers,maxDuration,memory,architecture,regions,functionFailoverRegions,supportsCancellation) was dropped at build time — only the top-levelfunctionsmap was honored. The build now feeds each service'sfunctionsto its lambdas for both single-lambda builders (@vercel/node, etc., viawriteBuildResultV3) and framework builders that readconfig.functions(e.g.@vercel/next, via the builder config). Derivedqueue/v2betaconsumer groups are now scoped by the owning service name so two services that declare the same function path + topic no longer collide.
13.32.1
24 Jun 2026Fix
vercel devfor standalone Node servers, including projects without apackage.json, and reuse the server process between requests.
13.32.0
24 Jun 2026Add
servicesas the canonical multi-service project configuration and keepexperimentalServicesV2as a deprecated backwards-compatible alias.Add an experimental container service runtime. A service with
runtime: "container"either builds itsDockerfile/Containerfileand 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
RUNsteps,
nativeoverlaystorage on the XFS/vercelvolume (deferring to the image'sstorage.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, andVERCEL_VCR_FORCE_LOGIN.Set the Node.js 20 discontinuation date to October 1, 2026.
13.31.1
23 Jun 2026Add support to
experimentalServicesV2for bindings invc dev
13.31.0
23 Jun 2026Add 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.
13.30.0
11 Jun 2026Add
hasFallback,htmlSize, andisDynamicRoutetoPrerenderThese 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):
13.29.1
11 Jun 2026Elevate maximum maxDuration to 1800s
13.29.0
10 Jun 2026Evaluate the
maxDurationupper bound at validation time soVERCEL_CLI_SKIP_MAX_DURATION_LIMITworks regardless of import order.The gate was read when
@vercel/build-utils'functionsSchemawas constructed and when the CLI compiled itsvercel.jsonvalidator — 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 withInvalid vercel.json - functions[...].maxDuration should be <= 900.@vercel/build-utilsnow exposesgetFunctionsSchema(), which reads the limit at call time (the existingfunctionsSchemaconst 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.
13.28.0
8 Jun 2026Add a per-route
hasPostponedsignal toPrerender.@vercel/build-utilsexposes a new optionalhasPostponed?: booleanfield onPrerender/PrerenderOptions. It is a tri-state:truewhen the route's.metapostponed state is present (React suspended during the build-time prerender),falsewhen the framework prerendered a Prerender route without postponing, andundefinedwhen the framework did not provide the signal.@vercel/nextpopulates it for app-router PPR routes (computed from the route's postponed state) and leaves itundefinedfor pages-router and other non-app-router prerenders. This is an additive, finer-grained signal — it does not change the existingchain/experimentalStreamingLambdaPathbehavior — so downstream consumers can distinguish a route that actually postponed from one that has PPR machinery but fully prerendered (e.g. undercacheComponents: true).
13.27.2
8 Jun 2026Gate the client-side 900-second
maxDurationupper bound behind theVERCEL_CLI_SKIP_MAX_DURATION_LIMITenvironment variable. The limit is now owned by a single helper in@vercel/build-utilsinstead of being hardcoded in multiple validators. When the variable is set to1, 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 anAccept: */*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.
13.27.1
4 Jun 2026Wire
experimentalServicesV2intofs-detectors.
13.27.0
3 Jun 2026Add isPackageInstalled util for detecting dependencies during build.
Fix Vercel Flags dependency detection for emitting datafiles during builds with OIDC tokens.
13.26.6
3 Jun 2026Remove the
servicesfield fromvercel.jsonand theVERCEL_USE_SERVICESgate.Add
experimentalServicesV2field tovercel.jsonimplementing the new schema for services.
13.26.4
28 May 2026Drop top-level
envsupport for the newservice-refshape for services.
13.26.3
27 May 2026Fix prebuilt deployments failing with "invalid relative path" when using the
--standaloneflag in pnpm monorepos by skipping external node_modules symlinks and copying traced files at their logical paths instead.
13.26.2
26 May 2026Cleanup getLambdaSupportsStreaming
13.26.1
22 May 2026Fix config.framework in deserializeBuildOutput
Support workflow-triggered job services in queue infrastructure
Add
isWorkflowTriggeredService()andisQueueBackedService()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.
13.26.0
19 May 2026Allow builder V2 to expose startDevServer.
Include framework slug in output/config.json
13.25.0
15 May 2026Add normalized entrypoint detector for runtime builders.
Add preDeployCommand for experimentalServices
13.24.0
13 May 2026Add support for env vars injection that reference other services in
serviceswith an explicitenvconfiguration.
13.23.0
11 May 2026Add project manifest to node builder.
servicesschema support
13.22.1
10 May 2026Disable response streaming for lambdas with
awsLambdaHandlerset insidegetLambdaSupportsStreaming. This closes a gap where non-Node builders (e.g.@vercel/redwood) constructedNodejsLambdawithawsLambdaHandlerbut no explicitsupportsResponseStreaming, causingfinalizeLambdato silently flip streaming on for AWS custom handlers. With the gate now enforced centrally infinalizeLambda, the equivalent@vercel/nodebuild-time check from #16266 is consolidated away — all builders go through the same gate.
13.22.0
9 May 2026Add service type to project manifest.
13.21.0
30 Apr 2026Upgrade to TypeScript 5.9
Minor Changes
Upgrade to TypeScript 5.9
13.20.0
22 Apr 2026Add framework to package manifest for python and backends builders.
Add shared build output deserialization helpers for existing callers.
13.19.1
20 Apr 2026Simplify streaming lambda check
13.19.0
17 Apr 2026Move Python workers to v2beta triggers with private routing
Added a shared build result validation helper in
@vercel/build-utilsfor existing callers.
13.18.0
17 Apr 2026Generate PROJECTMANIFEST in @vercel/backends for Node deployments.
13.17.1
16 Apr 2026Align deserialize logic with existing callers.
13.17.0
15 Apr 2026Support dynamically specifying crons from a python service
13.16.0
15 Apr 2026Add 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
13.15.0
14 Apr 2026Allow multiple v2beta triggers for a single Lambda when config is coming from services
Add deserialization utilities
13.14.2
11 Apr 2026Add
mountsupport for experimental services across config validation and service resolution.
13.14.1
10 Apr 2026Restore
finalizeLambda()to returnzipPath: nullfor 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
/apidirectory
13.14.0
8 Apr 2026Support configuration via vercel.toml
13.13.0
7 Apr 2026Extend
finalizeLambdawith pluggable ZIP strategy (createZip), pre-digest validation hook (validateZip), and optional trace tags. WidengetLambdaEnvironmentbuffer param to{ byteLength: number }.
13.12.2
1 Apr 2026Extract 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.