Packages

@vercel/node

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

Upgrading @vercel/node From 26.0.0 to 32.0.0

12 releases in betweennotes for 4

Reading releases, release notes and advisories…

32.0.0, 31.0.0, 30.0.0, 29.0.0 have no release note on GitHub or in the repository's changelog, so their breaking changes are missing from the counts below. The notes of 28.0.0, 27.0.0 list no breaking change or deprecation, which is rare for a major.
  1. 26.0.0yours
  2. 27.0.0major
  3. 2 releases
  4. 28.0.0major
  5. 1 release
  6. 29.0.0major
  7. 1 release
  8. 30.0.0major
  9. 31.0.0major
  10. 2 releases
  11. 32.0.0target
  12. 15 pre
?
changes to make
0
advisories fixed
?
new
2+
fixes

Counted from 4 of 12 release notes. Advisories are counted from the advisory database, in full.

Release by release

  1. 28.0.0 – 32.0.09 releases, nothing new or fixed; 8 without a note

  2. 27.0.2

    23 Oct 20261 fix
    • Fixed

      Report the runtime preset for services without a framework.

  3. 27.0.1nothing new or fixed in the note

  4. 27.0.0

    22 Oct 20261 fix
    • Fixed

      Remove the legacy BYOC extension's build-output collection and deserialization utilities, Lambda finalization and size validation, and serverless environment/streaming helpers. BYOC function preparation now uses vercel deploy describe.

4 internal lines (docs, tests, tooling) left out.

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.