Migrating to Next.js v16.3.0-canary.44
Version v16.3.0-canary.44 introduces 2 breaking changes. This guide details how to update your code.
Released: 6/7/2026
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
EcmascriptParsable::parse_originalturbopackMemoryLimitBreaking Changes
●Issue #1
Removed EcmascriptParsable::parse_original in Turbopack. Code relying on this specific parsing method will need to be updated to use alternative parsing mechanisms if available, or the functionality might need to be reimplemented.
●Issue #2
Removed turbopackMemoryLimit configuration option as it is deprecated and no longer functional. Users relying on this setting for memory management must look for alternative configuration methods or rely on default behavior.
Migration Steps
- 1Remove any usage of the removed turbopackMemoryLimit configuration.
- 2If using EcmascriptParsable::parse_original, update the code to use the replacement parsing mechanism.
Release Summary
This release focuses on internal cleanup and experimental feature enablement within Turbopack, notably removing dead configuration and adding an experimental eviction option.
Need More Details?
View the full release notes and all changes for Next.js v16.3.0-canary.44.
View Full Changelog