v16.1.0-canary.11
📦 next-jsView on GitHub →
✨ 5 features🐛 7 fixes🔧 5 symbols
Summary
This release focuses on Turbopack performance and stability, notably enabling the filesystem cache by default in dev and fixing rendering hangs. It also introduces deterministic manifest generation and improves Windows path handling for sourcemaps.
Migration Steps
- No immediate breaking changes were identified in these release notes. Review the changes for potential behavioral shifts if you heavily rely on specific internal behaviors.
- If you are using Turbopack in development, note that the filesystem cache is now enabled by default.
- If you encounter unexpected behavior related to dynamic promises during rendering abandonment, ensure your application logic is robust, as an underlying fix was applied.
- If you are working with Windows paths and sourcemaps, ensure your build tooling is up-to-date, as path conversion improvements were made.
✨ New Features
- Enabled filesystem cache by default for Turbopack in development mode.
- Added logging for generate params duration in development.
- Abstracted deployment ID access into a dedicated module.
- Implemented deterministic ordering for pages in the MappedPages structure.
- Ensured deterministic generation of functions-config-manifest.json.
🐛 Bug Fixes
- Fixed hanging dynamic promises when abandoning render in Concurrent Component (CC) logic.
- Fixed Windows path conversion issues when reading sourcemaps.
- Fixed preservation of all declarators in multi-declarator export statements within next-custom-transforms.
- Fixed Turbopack trace viewer empty space arrangement.
- Fixed Turbopack snapshotting behavior during continuous idle states and corrected spans.
- Fixed Turbopack fuzz command.
- Improved Turbopack eventual consistency.
🔧 Affected Symbols
MappedPagesfunctions-config-manifest.jsonnext-custom-transformsturbopackturbo-tasks-testing