next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 16.3.0 to 16.3.1
1 release in betweenevery note read
Security
19 advisories still affect 16.3.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 information disclosure in development server's Model Context Protocol endpointlow · GHSA-39w2-rjm5-chcv
Upgrading to 16.4.5 clears them.
Release by release
- New
Add
turbopack_ecmascriptandturbopack_wasm's embeded FS tointernal_assets_conditions - New
Allow literal exports in
'use cache'files - Fixed
Turbopack: Don't strip async-module runtime from shared runtime chunks
- Fixed
next/image: Preserve image response after optimization
- New
8 other lines we could not sort, mostly version bumps
- 16.3.1
Collapse nested promises in the analyzer
- 16.3.1
Bump @swc/helpers
- 16.3.1
Raise registration calls in hoisted modules to the top
- 16.3.1
Keep the dev validation worker alive across HMR updates
- 16.3.1
Discard only cache entries that predate a tag revalidation, and reuse completed entries
- 16.3.1
Encode the cache item name built by
unstable_cache - 16.3.1
Retain fewer stale cache versions and use a TTL, plus the mtime fallback
- 16.3.1
Revert i18n localization change for dynamic Pages API routes
3 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.