Migrating to Next.js v16.2.1-canary.10
Version v16.2.1-canary.10 introduces 1 breaking change. This guide details how to update your code.
Released: 3/26/2026
1
Breaking Changes
1
Migration Steps
3
Affected Symbols
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
Vc::resolveVc::to_resolvedtrack_modificationBreaking Changes
●Issue #1
Removed Vc::resolve(). All callsites must be migrated to use Vc::to_resolved() instead.
Migration Steps
- 1Replace all usages of Vc::resolve() with Vc::to_resolved().
Release Summary
This release focuses on internal improvements in turbo-tasks and turbopack, including a breaking API change in Vc resolution and enhancements to change detection mechanisms.
Need More Details?
View the full release notes and all changes for Next.js v16.2.1-canary.10.
View Full Changelog