@vercel/node
32.0.0 · 18 Nov 2026Apache-2.06.3M / weekRepositoryHomepagenpmAtom feed
408 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
5.9.6 – 5.9.72 releases that only update dependencies@vercel/build-utils 14.0.3Show each
- 5.9.78 Aug 2026@vercel/build-utils 14.0.3
- 5.9.67 Aug 2026@vercel/build-utils 14.0.2
5.9.5
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.
5.9.1 – 5.9.33 releases that only update dependencies@vercel/build-utils 13.36.3Show each
- 5.9.330 Jul 2026@vercel/build-utils 13.36.3
- 5.9.229 Jul 2026@vercel/build-utils 13.36.2
- 5.9.129 Jul 2026@vercel/build-utils 13.36.1
5.9.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.
5.8.23 – 5.8.275 releases that only update dependencies@vercel/build-utils 13.35.0Show each
- 5.8.2724 Jul 2026@vercel/build-utils 13.35.0
- 5.8.2616 Jul 2026@vercel/build-utils 13.34.0
- 5.8.2515 Jul 2026@vercel/build-utils 13.33.1
- 5.8.2413 Jul 2026@vercel/build-utils 13.33.0
- 5.8.239 Jul 2026@vercel/build-utils 13.32.3
5.8.22
27 Jun 2026Bridge WebSocket close to response close
Fix
vc buildrun from a monorepo subdirectory (gated behindVERCEL_RESOLVE_ROOT_DIRECTORY=1).When a project is linked in place (
apps/api/.vercel/project.json) andvc buildis run from that directory, the build previously treated the linked subdirectory as the repository root. Because the project's dependencies are typically hoisted to the monorepo root above it, this broke builds in several ways that share one root cause:With the flag enabled, a per-directory link is resolved like a repository-level link: the repository root is detected (workspace markers, then git) and the project is expressed as its path relative to that root, so the build is anchored correctly regardless of which directory the command is run from. The
rootDirectorysetting is interpreted relative to the link's location and honored when it points at a folder that exists; otherwise (e.g. the redundantapps/api/apps/apicase) it is ignored in favor of the link's own location and a warning is emitted. Standalone builds additionally preserve the package-manager symlinks (rather than skipping them) so dependencies resolve at runtime. Behavior is unchanged when the flag is not set.
Patch Changes
Bridge WebSocket close to response close
Fix
vc buildrun from a monorepo subdirectory (gated behindVERCEL_RESOLVE_ROOT_DIRECTORY=1).When a project is linked in place (
apps/api/.vercel/project.json) andvc buildis run from that directory, the build previously treated the linked subdirectory as the repository root. Because the project's dependencies are typically hoisted to the monorepo root above it, this broke builds in several ways that share one root cause:A
rootDirectorysetting that restates the link's own location (e.g.apps/apifor a link atapps/api) double-appended intoapps/api/apps/api, failing withENOENT … /apps/api/apps/api/.next/package.json.With
--standalone, the package-manager symlink that makes a dependency resolvable (apps/api/node_modules/hono→../../node_modules/.pnpm/.../hono) was skipped because its target pointed outside the subdirectory, so the deployed function failed at runtime withCannot find module 'hono'even though the dependency's files were packaged.Builders traced from the wrong root, so Next.js set an incorrect
outputFileTracingRoot/turbopack.root(Turbopack errors; Webpack.nft.jsonomits hoisted dependencies).
With the flag enabled, a per-directory link is resolved like a repository-level link: the repository root is detected (workspace markers, then git) and the project is expressed as its path relative to that root, so the build is anchored correctly regardless of which directory the command is run from. The
rootDirectorysetting is interpreted relative to the link's location and honored when it points at a folder that exists; otherwise (e.g. the redundantapps/api/apps/apicase) it is ignored in favor of the link's own location and a warning is emitted. Standalone builds additionally preserve the package-manager symlinks (rather than skipping them) so dependencies resolve at runtime. Behavior is unchanged when the flag is not set.
5.8.20 – 5.8.212 releases that only update dependencies@vercel/build-utils 13.32.1Show each
- 5.8.2124 Jun 2026@vercel/build-utils 13.32.1
- 5.8.2024 Jun 2026@vercel/build-utils 13.32.0
5.8.19
23 Jun 2026Add support to
experimentalServicesV2for bindings invc dev
Patch Changes
Add support to
experimentalServicesV2for bindings invc dev
5.8.7 – 5.8.1812 releases with no change for you11 dependency updates, 1 without a note@vercel/build-utils 13.31.0@vercel/error-utils 2.2.0Show each
- 5.8.1823 Jun 2026@vercel/build-utils 13.31.0
- 5.8.1711 Jun 2026@vercel/build-utils 13.30.0
- 5.8.1611 Jun 2026@vercel/build-utils 13.29.1
- 5.8.1510 Jun 2026@vercel/build-utils 13.29.0
- 5.8.148 Jun 2026@vercel/build-utils 13.28.0
- 5.8.138 Jun 2026@vercel/build-utils 13.27.2
- 5.8.124 Jun 2026@vercel/build-utils 13.27.1
- 5.8.113 Jun 2026@vercel/build-utils 13.27.0
- 5.8.103 Jun 2026@vercel/build-utils 13.26.6@vercel/error-utils 2.2.0
- 5.8.91 Jun 2026@vercel/build-utils 13.26.5
- 5.8.828 May 2026no note
- 5.8.728 May 2026@vercel/build-utils 13.26.4
5.8.6
27 May 2026Allow opting into the Web API handler interface (
Request→Response) from the staticconfigexport of a Node.js Serverless Function by settinguseWebApi: true.
Patch Changes
Allow opting into the Web API handler interface (
Request→Response) from the staticconfigexport of a Node.js Serverless Function by settinguseWebApi: true.
5.8.5
26 May 2026Pass service type and framework to node manifest.
Patch Changes
Pass service type and framework to node manifest.
5.8.1 – 5.8.44 releases that only update dependencies@vercel/build-utils 13.26.1Show each
- 5.8.422 May 2026@vercel/build-utils 13.26.1
- 5.8.319 May 2026@vercel/build-utils 13.26.0
- 5.8.215 May 2026@vercel/build-utils 13.25.0
- 5.8.113 May 2026@vercel/build-utils 13.24.0
5.8.0
11 May 2026Add project manifest to node builder.
Minor Changes
Add project manifest to node builder.
5.7.17
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.
Patch Changes
Disable 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.
5.7.16
9 May 2026Disable response streaming for AWS custom handler lambdas
Patch Changes
Disable response streaming for AWS custom handler lambdas
5.7.15
30 Apr 2026node: Replace deprecated
url.parse()with WHATWG URL API to silence DEP0169 deprecation warning on cold starts
5.7.8 – 5.7.135 releases that only update dependencies@vercel/build-utils 13.20.0Show each
- 5.7.1322 Apr 2026@vercel/build-utils 13.20.0
- 5.7.1220 Apr 2026@vercel/build-utils 13.19.1
- 5.7.1117 Apr 2026@vercel/build-utils 13.19.0
- 5.7.1017 Apr 2026@vercel/build-utils 13.18.0
- 5.7.816 Apr 2026@vercel/build-utils 13.17.1
5.7.7
15 Apr 2026Fix bundled vanilla Node API routing for projects that build from a root directory.
Patch Changes
Fix bundled vanilla Node API routing for projects that build from a root directory.
5.7.1 – 5.7.66 releases that only update dependencies@vercel/build-utils 13.16.0Show each
- 5.7.615 Apr 2026@vercel/build-utils 13.16.0
- 5.7.514 Apr 2026@vercel/build-utils 13.15.0
- 5.7.411 Apr 2026@vercel/build-utils 13.14.2
- 5.7.310 Apr 2026@vercel/build-utils 13.14.1
- 5.7.28 Apr 2026@vercel/build-utils 13.14.0
- 5.7.17 Apr 2026@vercel/build-utils 13.13.0
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.