next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 16.4.1 to 16.4.2
1 release in betweenevery note read
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 3
- fixes
Security
7 advisories still affect 16.4.2
- Next.js: SVG rejection bypass in the image optimizationmoderate · GHSA-7qx7-33qx-rqx2
- Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routesmoderate · GHSA-f3mh-rxg3-f5g2
- Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()moderate · GHSA-mfr8-8qww-v76h
Upgrading to 16.4.5 clears them.
Release by release
- Fixed
next-code-frame: Snap visible window to char boundaries
- Fixed
Fix two GC paths that leave half-torn-down dependency edges
- Fixed
Fix Turbopack lazy dynamic-import chunk-list collisions
- Fixed
5 other lines we could not sort, mostly version bumps
- 16.4.2
turbo-tasks snapshot consistency fixes (#99644, #99732, #99649)
- 16.4.2
Turbopack: Backport Pages Router dev module graph chaining (#98823, #99910, #100091)
- 16.4.2
Turbopack: Ignore realpath errors during module resolution, matching node's behavior
- 16.4.2
Backport docs fixes since v16.4.0
- 16.4.2
Backport additional documentation fixes since v16.4.0
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.