· ai-devtools
next.js 16.5.0-canary.31 released with build and turbopack perf updates
The latest canary release, next.js 16.5.0-canary.31, introduces performance enhancements, notably lazily requiring page-data helpers within build/utils, as noted in 100822.
The latest canary release, next.js 16.5.0-canary.31, introduces performance enhancements, notably lazily requiring page-data helpers within build/utils, as noted in #100822.
Additionally, this version features a change to canonicalize async loader availability within Turbopack, tracked under #100705. A special acknowledgment goes to @sokra for contributing to this release.
In the preceding release, next.js 16.5.0-canary.30, several core changes addressed developer workflows. These included ignoring expected upgrade nudges in Agent Feedback (#100840) and adding model metadata to Agent Feedback (#100806).
For improved dependency handling, the version switches to using fast-jwt instead of jsonwebtoken (#100818). Updates were also made to font data (#100813), and Turbopack now waits for trace file changes following format errors (#99847).
Furthermore, a new CLI was added for reviewing agent feedback (#100739). Miscellaneous updates saw the addition of criteria for Vercel Agent code review (#100846) and the introduction of the experimental.hydrationChangeEvent flag (#99610).
Turbopack saw further refinement, moving a reference to bincode's virtue dependency into a vercel-labs owned fork repository (#100847). Other fixes involved addressing the `export const foo = function bar(){}` issue in server reference transform (#100830) and fixing the build harness for nested-deps-app-router-many-pages (#100820).
The release also saw various tooling improvements across persistence and CI, such as turbo-persistence using partition_point for batch lookup bounds (#100821) and CI not running non-adapter + cache components deploy tests in PRs (#100824). Documentation was also updated regarding dynamic rendering claims for cookies and the Suspense requirement for connection() with Cache Components.
This release benefited from assistance from several contributors, including @acdlite, @bgw, @aurorascharff, @sokra, @mischnic, @devjiwonchoi, @lukesandberg, and @icyJoseph.
