· javascript
next.js 16.5.0-canary.35 released with error handling fixes, cache fixes, and docs clarifications
The latest release, next.js 16.5.0-canary.35, brings several important updates for developers working with the framework.
Among the core changes, the update addresses handling cancellation errors during response clone cleanup, tracked under issue #100961. Additionally, a reversion was made for "Fix App Router locale path matching with Pages i18n," referenced as #98726.
Another key fix involves resolving the prerendering of caught `'use cache'` errors, detailed in #100956.
In terms of documentation refinements, the team clarified the status of blocking route responses, noted in #100191. Further documentation updates include noting the per-route cost of boundary files, cached Route Handler checks, and per-instance rate limits (#100985), and clarifying unstable_cache cross-deployment persistence (#100983).
For tooling, Turbopack now only adds the Pages client entry when Pages routes are present (#100896). It also features an enhancement to drop ASTs of tree-shaken modules (#100871).
Other notable technical improvements include Turbopack using memchr3 for source position scanning and counting astral chars as two UTF-16 columns (#100919). Furthermore, Turbopack will now report chunk group consistency errors instead of panicking (#100923).
