@vercel/next
31.0.2 · 20 Nov 2026Apache-2.05.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/next From 3.1.13 to 31.0.2
337 releases in betweennotes for 92
Release by release
27.0.0 – 31.0.212 releases, nothing new or fixed; 11 without a note
- Fixed
Report the runtime preset for services without a framework.
- Fixed
21.0.0 – 26.0.111 releases, nothing new or fixed in the notes
- Fixed
Reject immutable static assets in Next.js static export builds when not using the adapter.
- Fixed
17.0.0 – 20.0.04 releases, nothing new or fixed in the notes
- Fixed
Preserve function affinity when building grouped Next.js functions.
- Fixed
14.0.0 – 15.0.24 releases, nothing new or fixed in the notes
- New
Expose a development manifest for static Next.js App Router handlers and Pages API routes, including functions without triggers, deployment output identities, local HTTP invocation targets, and normalized Queue and Schedule trigger metadata. Use the project's isolated development configuration and diagnose unsupported trigger mappings and conflicting output identities.
- Fixed
Disable adapters by default
- New
5 other lines we could not sort, mostly version bumps
- 4.3.21
Revert "Fix edge cases with internal redirect sorting"
- 4.3.14
Revert "[build-utils] Fix corepack
packageManagerdetection on monorepos" - 4.3.10
Revert "Revert "Revert "Fix corepack
packageManagerdetection on monorepos""" - 4.3.9
Revert "Revert "Fix corepack
packageManagerdetection on monorepos"" - 4.3.6
Revert "Fix corepack
packageManagerdetection on monorepos"
37 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.