next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.2.1 to 13.2.2
1 release in betweenevery note read
Security
29 advisories still affect 13.2.2
- 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
cssnano-simple: Merge into next repo
- New
Support
server-onlyinside pages/api - New
Add relative app dir field
- New
Add @latest to next/font codemod warning
- New
11 other lines we could not sort, mostly version bumps
- 13.2.2
Dedupe next/font preload tags
- 13.2.2
Print command for current packet manager in @next/font warning
- 13.2.2
Loader refactoring
- 13.2.2
Revert "Support
server-onlyinside pages/api" - 13.2.2
Update server reference syntax and tests
- 13.2.2
Refactor style loader code
- 13.2.2
Update router filter to be less sensitive
- 13.2.2
Update fetch cache internal handling
- 13.2.2
Upgrade precompiled react packages
- 13.2.2
Refactor route types to include rewrites and redirects
21 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.