Packages

@vercel/next

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

Upgrading @vercel/next From 16.0.0 to 31.0.2

29 releases in betweennotes for 18

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

Counted from 18 of 29 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. 17.0.0 – 20.0.04 releases, nothing new or fixed in the notes

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