next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.0.4 to 13.0.5
1 release in betweenevery note read
Security
29 advisories still affect 13.0.5
- 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
- New
Add force-static handling for app dir
- New
Add experimental outputFileTracingIgnores config
- New
Add fallback aliases for React
- New
Add links to PR template
- New
14 other lines we could not sort, mostly version bumps
- 13.0.5
Remove unnecessary async function when preloading async components
- 13.0.5
Leverage outputFileTracingIgnores for next-server trace as well
- 13.0.5
Remove
unstable_revalidate - 13.0.5
types: Better type definition for internal utils
- 13.0.5
Eagerly build swc binaries on change
- 13.0.5
Remove the timestamp query for CSS resources
- 13.0.5
Update experimental skipTrailingSlashRedirect handling
- 13.0.5
Alias esm next document to avoid mismatch react context
- 13.0.5
Remove app routes from _devPagesManifest
- 13.0.5
Remove unused
use-sync-external-storedependency
24 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.