Packages

@vercel/next

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

Upgrading @vercel/next From 19.0.0 to 31.0.2

26 releases in betweennotes for 15

31.0.0, 30.0.0, 29.0.0, 28.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 notes of 27.0.0, 26.0.0, 25.0.0, 24.0.0, 23.0.0, 22.0.0, 21.0.0, 20.0.0 list no breaking change or deprecation, which is rare for a major.
  1. 19.0.0yours
  2. 20.0.0major
  3. 1 release
  4. 21.0.0major
  5. 22.0.0major
  6. 1 release
  7. 23.0.0major
  8. 3 releases
  9. 24.0.0major
  10. 25.0.0major
  11. 26.0.0major
  12. 2 releases
  13. 27.0.0major
  14. 1 release
  15. 28.0.0major
  16. 1 release
  17. 29.0.0major
  18. 1 release
  19. 30.0.0major
  20. 2 releases
  21. 31.0.0major
  22. 1 release
  23. 31.0.2target
  24. 19 pre
?
changes to make
0
advisories fixed
?
new
2+
fixes

Counted from 15 of 26 release notes. Advisories are counted from the advisory database, in full.

Release by release

  1. 27.0.0 – 31.0.212 releases, nothing new or fixed; 11 without a note

  2. 26.0.2

    23 Oct 20261 fix
    • Fixed

      Report the runtime preset for services without a framework.

  3. 21.0.0 – 26.0.111 releases, nothing new or fixed in the notes

  4. 20.0.1

    6 Oct 20261 fix
    • Fixed

      Reject immutable static assets in Next.js static export builds when not using the adapter.

  5. 20.0.0nothing new or fixed in the note

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