next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.5.2 to 13.5.3
1 release in betweenevery note read
Security
36 advisories still affect 13.5.3
- 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
turbopack: Construct output path with distDir next.js config
- New
Add experimental.strictNextHead to Turbopack
- New
Add trailingSlash, basePath, and assetPrefix to Turbopack
- New
Allow filtering individual test cases inside test files
- New
21 other lines we could not sort, mostly version bumps
- 13.5.3
Only put css in entry_css_files
- 13.5.3
Update taskfile to generate types during
build - 13.5.3
Capitalize compiling log
- 13.5.3
Split prerending by route kind
- 13.5.3
turbopack: Update the
next/dist/esmrewriteResolvePlugin - 13.5.3
Remove --watch from
generate_typestask - 13.5.3
Remove the left padding in
next infooutput - 13.5.3
Revert "fix: Invoke cancel, only if the stream is not closed (#55684)"
- 13.5.3
turbopack: Rewrite ESM modules to CJS during client transition
- 13.5.3
Remove unused internal env var
28 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.