next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 14.0.0 to 14.0.1
1 release in betweenevery note read
Security
36 advisories still affect 14.0.1
- 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 Next.js 14 codemods to CLI output.
- New
debug: Add tags to next build traces to track build configuration in the .next/trace file
- New
Add node-pty to externals list
- New
Support viewport export via TS Plugin
- New
5 other lines we could not sort, mostly version bumps
- 14.0.1
OpenTelemetry: Propagate a configured context(s) to root requests
- 14.0.1
Await the flush of the trace write stream to make sure trace file is written
- 14.0.1
Update font data
- 14.0.1
Improve error for missing default export in dynamic metadata routes
- 14.0.1
Update React from 8c8ee9ee6 to 0c6348758 and types
23 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.