@vercel/node
32.0.0 · 18 Nov 2026Apache-2.06.3M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/node From 1.8.3 to 32.0.0
397 releases in betweennotes for 285
Reading releases, release notes and advisories…
- 6+
- changes to make
- 0
- advisories fixed
- 34+
- new
- 71+
- fixes
Counted from 285 of 397 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking5.5.33
- Breaking5.0.0
- Breaking4.0.0
- Breaking3.0.0
- Deprecated8.1.0
- Deprecated3.0.16
Security
- 3.2.0
Update undici dep to address vulnerabilities
Release by release
28.0.0 – 32.0.09 releases, nothing new or fixed; 8 without a note
- Fixed
Report the runtime preset for services without a framework.
- Fixed
27.0.1nothing new or fixed in the note
- 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.
- Fixed
26.0.0nothing new or fixed in the note
- New
Add
functions[glob].installCommand. For matching@vercel/nodefunctions, an empty string skips the dependency install and a non-empty value runs instead of the default install. Builds warn when the property matches functions of other runtimes, which ignore it.
- New
- Fixed
Display the edge middleware deprecation warning in yellow with a bold WARNING! prefix during builds and at
vercel devstartup. Add an optional builder hook for detecting startup warnings without starting a development server.
- Fixed
22.0.0 – 24.0.26 releases, nothing new or fixed in the notes
2 other lines we could not sort, mostly version bumps
- 5.5.6
Revert "Remove getSpawnOptions"
- 3.0.7
Revert "[next][node][redwood][remix] Update @vercel/nft (#10540)"
257 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.