@next/codemod
16.4.6 · 9 Nov 2026MIT253.5k / weekRepositoryHomepagenpmAtom feed
Upgrading @next/codemod From 11.1.0 to 11.1.4
4 releases in betweennotes for 3
Reading releases, release notes and advisories…
Release by release
11.1.3 – 11.1.42 releases, nothing new or fixed; 1 without a note
- Fixed
Ensure custom app regex is correct for Windows
- Fixed
- New
Add missing fields to
NextConfigtype - New
Add support for dynamic HTML
- New
Support suspense in next dynamic
- New
Add proper error when failing to load next.config.js
- New
18 other lines we could not sort, mostly version bumps
- 11.1.2
getServerSideProps should support props value as Promise
- 11.1.1
Next.js swc publish flow
- 11.1.1
Use a shared worker pool for collecting page data and static page generation
- 11.1.1
Use @next scope for native packages
- 11.1.1
Clean up
Documentin preparation for streaming - 11.1.1
Render as a concatenation of streams
- 11.1.1
Bypass webpack compilation for precompiled @next/polyfills-nomodule
- 11.1.1
Remove duplicate doctypes
- 11.1.1
Update to latest babel versions
- 11.1.1
Improve jaeger traces
58 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.