next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 15.0.8 to 15.1.0
1 release in betweenevery note read
Security
39 advisories still affect 15.1.0
- 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 expireTag and expirePath APIs
- New
Add BackendOptions and allow to disable dependencies, children and storage
- New
Add experimental
clientSegmentCacheflag - New
Add
compiler.defineoption
- New
77 other lines we could not sort, mostly version bumps
- 15.1.0
Expand
server-source-mapsscenarios to cover Edge runtime - 15.1.0
Capture console issues as console errors
- 15.1.0
Move client build ID to a global variable
- 15.1.0
Bypass source map dev middleware for client chunks
- 15.1.0
Improve
no-img-elementlint error message - 15.1.0
Combine bound
"use cache"closure args into a single parameter - 15.1.0
Omit unused args when calling
"use cache"functions - 15.1.0
Improved network url in (dev) cli
- 15.1.0
Bump the monorepo packages TypeScript to
5.6.3 - 15.1.0
Bump
@capsizecss/metricsto 3.4.0 for Geist Google Font
241 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.