Next.js shipped the stable v16.4.3 and five v16.5.0 canaries this week. The stable release is a small bug-fix backport, while the canaries are mostly about caching and Turbopack.
Next.js is the React-based web framework from Vercel. It has 61,775,810 weekly downloads on npm.
The stable v16.4.3 came out on October 23. In the four days after that, five canaries followed, from v16.5.0-canary.25 to canary.29. The stable line is quiet. The canary line is not.
그림: nextjs.org
The release notes say it up front: this release backports bug fixes and does not include everything pending on canary. The list is short.
- Fixes Google font URLs with no file extension in both bundlers, Turbopack and webpack (#100277)
proxy.tsno longer loads the app-page runtime (#100423)- Server bootstrap no longer loads the standalone React build (#100610)
- OpenTelemetry request traces stay together as one (#100542)
- Reverts one Turbopack change to how loaders are invalidated (#100438)
The rest is housekeeping, such as release-bot credentials and pinned test dependencies. There are no features.
그림: vercel.com
v16.5.0 canaries, October 23 to 27
| canary.25 | Oct 23 | Reverts a webpack loader dependency change (#100634), caches bundle analysis per output file (#100475) |
| canary.26 | Oct 23 | Turbopack trace format TRACEv1 (#99781), fixes navigation from global-not-found to app routes (#100592) |
| canary.27 | Oct 24 | Fixes the dist lock file on filesystems such as NFS (#100684) |
| canary.28 | Oct 26 | Draft mode with Cache Components (#100728), a hanging HTML response after a use cache error (#100673), drops a quadratic app-path scan during build (#100615) |
| canary.29 | Oct 27 | Persists fully static PPR payloads in the filesystem cache (#100759), keeps the storage cache in Docker environments (#100790) |
The cache lines pile up in canary.28 and 29, including the fix for an HTML response that hung after an error in use cache. canary.29 also upgrades React and bumps the image library sharp to 0.35.5.
If you are on v16.4.x, I would move to v16.4.3. The list is small and has no new features, so there is little to lose. If you ever hit the font URL or proxy.ts problems, even more so.
I would stay off the canaries. Teams that use Cache Components or use cache should still read the canary.28 items, though. A problem you have been chasing may be written down there.
One thing I don't know yet: how these fixes will look inside the v16.5 stable release. The release notes alone don't tell me.
- On GitHub Trending (CSS), Nutlope/hallmark gained 8,612 stars this week
- Chrome posted What's New in WebGPU (Chrome 155-156)
- WebKit introduced the features in Safari 27.2