@vercel/next
31.0.2 · 20 Nov 2026Apache-2.05.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/next From 4.2.14 to 4.21.7
157 releases in betweennotes for 51
Release by release
- Fixed
Clean up the
NEXT_EXPERIMENTAL_LARGE_FUNCTIONSflag: routes that individually exceed the default packing budget are now always emitted as their own function, no opt-in required.
- Fixed
- 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-vercelto0.0.1-beta.27, which includes the postponed state byte-length fix for partially prerendered output.
- Fixed
4.10.4 – 4.21.496 releases, no release note
- Fixed
Fix node middleware with hoisted distDir
- Fixed
Fix case for _next/data for i18n-basepath-middleware
- Fixed
- New
Added support for partial routes defining a source page by adding lambdas for these routes
- New
4.10.1no release note
- New
Adds support for user configured
preferredRegionfor Node.js Functions
- New
- Fixed
Simplify experimental triggers
- Fixed
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"
1 internal line (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.