●Change8

Migrating to Next.js v16.2.1-canary.20

Version v16.2.1-canary.20 introduces 1 breaking change. This guide details how to update your code.

Released: 4/4/2026

1
Breaking Changes
1
Migration Steps
5
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

FileSystemPath::value_to_stringValueToStringRef::to_string_refResolveRawVcFutureResolveVcFutureToResolvedVcFuture

Breaking Changes

●Issue #1

Turbopack removed FileSystemPath::value_to_string in favor of ValueToStringRef::to_string_ref. Code relying on the old method will need updating to use the new reference-based approach.

Migration Steps

  1. 1
    If you were using FileSystemPath::value_to_string in Turbopack related code, replace it with ValueToStringRef::to_string_ref.

Release Summary

This release improves the development server experience with better error messages and automatic restarts, and introduces experimental configuration options for SWC. It also includes several internal Turbopack and turbo-tasks refactorings.

Need More Details?

View the full release notes and all changes for Next.js v16.2.1-canary.20.

View Full Changelog