next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 13.1.1 to 13.1.2
1 release in betweenevery note read
Security
29 advisories still affect 13.1.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
Add special error message for class component in server component
- New
Add updated flush handling on sigterm
- New
standalone: Allow configuring
HOSTNAMEvia env var - New
Add experimental pre-compiled next-server
- New
19 other lines we could not sort, mostly version bumps
- 13.1.2
Update license year
- 13.1.2
Move core files to src folder and move JS files to TypeScript
- 13.1.2
types: Remove config.experimental.profiling
- 13.1.2
Update server-external-packages to include aws-crt
- 13.1.2
Collapse sequences of call stack frames from React and Next.js in the error overlay
- 13.1.2
Update json5 dependency to latest
- 13.1.2
Improve errors caused by client hook called in a server component
- 13.1.2
Remove unused
target: es5fromtsconfig.json - 13.1.2
Make static page prefetch apply on navigation in app dir
- 13.1.2
Improve errors caused by Next.js client hook called in a server component
68 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.