what stackpulse tracks
Next.js releases from GitHub
StackPulse watches Next.js release notes and keeps the original source link close to every summary.
The React Framework for the Web StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Next.js release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This canary release improves prerendered Link header handling during revalidation and reduces header allocations in NodeNextResponse. It also changes the image optimizer transform package path and includes updates to Request Insights, build analysis, Turbopack, and documentation.
Next.js canary users working with the image optimizer transform public API, prerendered links, or Request Insights are most directly affected.
Update imports if you use `next/image-optimizer-transform`, following its move to the `next/experimental` namespace.
This prerelease improves Request Insights with persistent session history, route-module loading and preparation details, and more request and fetch information. It also adds automatic compression for route-handler responses that are not already compressed and includes several Turbopack and tooling fixes.
Next.js users, particularly those using Request Insights, route handlers, or `next/image-optimizer-transform`, may be affected.
If your code imports `optimizeImage` from `next/image-optimizer-transform`, review and update that usage because the release removes it from the public API.
This canary adds internal image redirects to `next/image` and introduces Request Insights filters and pause controls. It also includes Turbopack, tracing, image-optimizer, and configuration improvements, plus assorted fixes.
Next.js canary users are affected, particularly those using `experimental.lockDistDir` or the updated image and Request Insights functionality.
If your configuration uses `experimental.lockDistDir`, remove that option before upgrading.