Packages

@vercel/node

32.0.0 · 18 Nov 2026Apache-2.06.3M / weekRepositoryHomepagenpmAtom feed

Your version

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

  1. 5.9.6 – 5.9.72 releases that only update dependencies@vercel/build-utils 14.0.3Show each
  2. 5.9.5

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

  3. 5.9.1 – 5.9.33 releases that only update dependencies@vercel/build-utils 13.36.3Show each
  4. 5.9.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.

  5. 5.8.23 – 5.8.275 releases that only update dependencies@vercel/build-utils 13.35.0Show each
  6. 5.8.22

    27 Jun 2026
    • Bridge WebSocket close to response close

    • Fix vc build run from a monorepo subdirectory (gated behind VERCEL_RESOLVE_ROOT_DIRECTORY=1).

      When a project is linked in place (apps/api/.vercel/project.json) and vc build is 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 rootDirectory setting is interpreted relative to the link's location and honored when it points at a folder that exists; otherwise (e.g. the redundant apps/api/apps/api case) 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.

  7. 5.8.20 – 5.8.212 releases that only update dependencies@vercel/build-utils 13.32.1Show each
  8. 5.8.19

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

  9. 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
  10. 5.8.6

    27 May 2026
    • Allow opting into the Web API handler interface (Request → Response) from the static config export of a Node.js Serverless Function by setting useWebApi: true.

  11. 5.8.5

    26 May 2026
    • Pass service type and framework to node manifest.

  12. 5.8.1 – 5.8.44 releases that only update dependencies@vercel/build-utils 13.26.1Show each
  13. 5.8.0

    11 May 2026
    • Add project manifest to node builder.

  14. 5.7.17

    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.

  15. 5.7.16

    9 May 2026
    • Disable response streaming for AWS custom handler lambdas

  16. 5.7.15

    30 Apr 2026
    • node: Replace deprecated url.parse() with WHATWG URL API to silence DEP0169 deprecation warning on cold starts

  17. 5.7.8 – 5.7.135 releases that only update dependencies@vercel/build-utils 13.20.0Show each
  18. 5.7.7

    15 Apr 2026
    • Fix bundled vanilla Node API routing for projects that build from a root directory.

  19. 5.7.1 – 5.7.66 releases that only update dependencies@vercel/build-utils 13.16.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.