Packages

@vercel/node

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

Upgrading @vercel/node From 27.0.1 to 32.0.0

10 releases in betweennotes for 2

Reading releases, release notes and advisories…

Other targets from 27.0.1Newest 27.x27.0.2
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 note of 28.0.0 lists no breaking change or deprecation, which is rare for a major.
  1. 27.0.1yours
  2. 1 release
  3. 28.0.0major
  4. 1 release
  5. 29.0.0major
  6. 1 release
  7. 30.0.0major
  8. 31.0.0major
  9. 2 releases
  10. 32.0.0target
  11. 15 pre
?
changes to make
0
advisories fixed
?
new
1+
fix

Counted from 2 of 10 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.

2 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.