v16.1.0-canary.14
📦 next-jsView on GitHub →
✨ 4 features🐛 4 fixes🔧 5 symbols
Summary
This release focuses on internal Turbopack optimizations via bincode serialization and fixes for next/image query string handling. It also includes documentation updates for Firebase App Hosting and dependency cleanup.
Migration Steps
- Review the release notes for any changes relevant to your specific project configuration, especially concerning Turbopack or Next.js image handling.
- Update your dependencies to the latest version.
- If you were using `vitest` or `vite` directly in your project dependencies (and not just as dev dependencies managed by the framework), verify if their removal from the dependency tree affects your setup.
- If you are using local images with next/image and they were not loading correctly without a protocol in the src attribute, this version should resolve the issue by correctly handling the `?dpl` query string.
✨ New Features
- Added selective draggable content for devtools.
- Optimized server module map proxy creation to occur only once.
- Introduced custom bincode serialization helpers, traits, and reader/writer implementations for Turbopack.
- Added Firebase App Hosting to the deployment guide.
🐛 Bug Fixes
- Fixed next/image to include the `?dpl` query string for local images without static imports.
- Fixed next/image to handle `?dpl` for source URLs without a protocol.
- Fixed missing NFT file in test suite.
- Improved Turbopack performance by avoiding clones in RopeReader.
🔧 Affected Symbols
next/imageRopeReaderTurboBincodeEncoderTurboBincodeDecoderserver module map proxy