next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.2.3 to 13.2.4
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 19
- new
- 22
- fixes
Before you upgrade
Tick each one off as you go- Breaking13.2.4
Security
29 advisories still affect 13.2.4
- Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are usedcritical · GHSA-2464-fhr4-w9xw
- Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are usedcritical · GHSA-2xp9-vwfh-vxw4
- Next.js has a Middleware / Proxy bypass in Pages Router applications using i18nhigh · GHSA-36qx-fr4f-26g5
Upgrading to 15.5.29 clears them.
Release by release
- Breaking
Remove extra exports from filter utils
- New
Support path aliases from
tsconfig/jsconfig - New
Support named exports for server references
- New
Add request callback in Flight client
- Breaking
20 other lines we could not sort, mostly version bumps
- 13.2.4
Check if server error already had its message updated
- 13.2.4
List unsupported Turbopack config keys
- 13.2.4
Update vendored React packages to next-41110021f
- 13.2.4
Updates
next/imageeslint message to denote that costs may be incurred. - 13.2.4
Use separate workers for webpackBuildWorker
- 13.2.4
Update static build workers
- 13.2.4
Refactor build context for better plugin state sharing
- 13.2.4
Disallow wildcard export in server entries
- 13.2.4
Update client router filter to separate redirects handling
- 13.2.4
Pass through original matcher source in manifest
44 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.