Packages

@vercel/next

31.0.2 · 20 Nov 2026Apache-2.05.8M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/next From 4.5.1 to 4.21.7

124 releases in betweennotes for 27

Other targets from 4.5.1Latest31.0.2
  1. 4.5.1yours
  2. 123 releases
  3. 4.21.7target
?
changes to make
0
advisories fixed
16+
new
20+
fixes

Counted from 27 of 124 release notes. Advisories are counted from the advisory database, in full.

Release by release

  1. 4.21.7

    20 Aug 20261 fix
    • Fixed

      Clean up the NEXT_EXPERIMENTAL_LARGE_FUNCTIONS flag: routes that individually exceed the default packing budget are now always emitted as their own function, no opt-in required.

  2. 4.21.6

    15 Aug 20262 fixes
    • Fixed

      Declare the postponed state length of a partially prerendered output in bytes, so the CDN splits the output at the right offset when the state contains a multi-byte character.

    • Fixed

      Update @next-community/adapter-vercel to 0.0.1-beta.27, which includes the postponed state byte-length fix for partially prerendered output.

  3. 4.10.4 – 4.21.496 releases, no release note

  4. 4.10.3

    22 Jul 20252 fixes
    • Fixed

      Fix node middleware with hoisted distDir

    • Fixed

      Fix case for _next/data for i18n-basepath-middleware

  5. 4.10.2

    18 Jul 20251 new
    • New

      Added support for partial routes defining a source page by adding lambdas for these routes

  6. 4.10.1no release note

  7. 4.10.0

    10 Jul 20251 new
    • New

      Adds support for user configured preferredRegion for Node.js Functions

  8. 4.9.5

    4 Jul 20251 fix
    • Fixed

      Simplify experimental triggers

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.