@vercel/node
32.0.0 · 18 Nov 2026Apache-2.06.3M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/node From 3.0.1 to 3.2.29
65 releases in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 3
- new
- 16
- fixes
Before you upgrade
Tick each one off as you go- Deprecated3.0.16
Security
- 3.2.0
Update undici dep to address vulnerabilities
Release by release
- Fixed
Update express even more
- Fixed
- Fixed
Bump express version
- Fixed
3.2.5 – 3.2.2723 releases, nothing new or fixed in the notes
- Fixed
Upgrade to @vercel/nft 0.27.3 with a bug fix for browser mapping support
- Fixed
3.2.1 – 3.2.33 releases, nothing new or fixed in the notes
- Security
Update undici dep to address vulnerabilities
- New
Ignore
shouldAddHelperswhen exporting a server to match production
- Security
- Fixed
Upgrade to @vercel/nft 0.27.2 with browser remapping support
- Fixed
3.1.2 – 3.1.65 releases, nothing new or fixed in the notes
1 other line we could not sort, mostly version bumps
- 3.0.7
Revert "[next][node][redwood][remix] Update @vercel/nft (#10540)"
62 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.