Packages

@vercel/node

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

Upgrading @vercel/node From 3.0.22 to 3.2.29

44 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 3.0.22Latest32.0.0
  1. 3.0.22yours
  2. 14 releases
  3. 3.2.0security
  4. 28 releases
  5. 3.2.29target
0
changes to make
0
advisories fixed
3
new
6
fixes

Security

  • Update undici dep to address vulnerabilities

    3.2.0

Release by release

  1. 3.2.29

    9 Dec 20241 fix
    • Fixed

      Update express even more

  2. 3.2.28

    4 Dec 20241 fix
    • Fixed

      Bump express version

  3. 3.2.5 – 3.2.2723 releases, nothing new or fixed in the notes

  4. 3.2.4

    16 Jul 20241 fix
    • Fixed

      Upgrade to @vercel/nft 0.27.3 with a bug fix for browser mapping support

  5. 3.2.1 – 3.2.33 releases, nothing new or fixed in the notes

  6. 3.2.0

    Security fix25 Jun 20241 new
    • Security

      Update undici dep to address vulnerabilities

    • New

      Ignore shouldAddHelpers when exporting a server to match production

  7. 3.1.7

    7 Jun 20241 fix
    • Fixed

      Upgrade to @vercel/nft 0.27.2 with browser remapping support

  8. 3.1.2 – 3.1.65 releases, nothing new or fixed in the notes

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