next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.0.2 to 13.0.3
1 release in betweenevery note read
Security
29 advisories still affect 13.0.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
Add telemetry for turbotrace
- New
Add lazy initialize of router cache nodes
- New
Add telemetry for @next/font
- New
Add --no-mangling to next build + fix --profile option
- New
22 other lines we could not sort, mostly version bumps
- 13.0.3
Bump @typescript-eslint/parser version to support TS 4.8
- 13.0.3
Re-enable sandbox cache and update AsyncLocalStorage usage
- 13.0.3
Check properly whether SWC is used or not when using forceSwcTransforms
- 13.0.3
Show inlined error if the "use client" directive is not before other statements/expressions
- 13.0.3
Refactor error codes in the TS plugin
- 13.0.3
Aggregate updates using
addStatusHandlerandPromise.resolveinstead ofsetTimeout - 13.0.3
Rename RSC and Router headers
- 13.0.3
Include @prisma/client in default external packages
- 13.0.3
Replace global with globalThis
- 13.0.3
Colocate styles with special entries
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.