●Change8

Migrating to Next.js v16.2.0-canary.62

Version v16.2.0-canary.62 introduces 2 breaking changes. This guide details how to update your code.

Released: 2/25/2026

2
Breaking Changes
2
Migration Steps
5
Affected Symbols

⚠️ Check Your Code

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

unstable_instantworker_threadsloading.jsnext-swcNEXT_TEST_NATIVE_DIR

Breaking Changes

●Issue #1

Throw an error when `unstable_instant` is used within a Client Component. This feature is intended only for Server Components.

●Issue #2

Turbopack build process has changed: it is no longer automatically included in `pnpm build`. Users must now explicitly run `pnpm build-all` to include Turbopack compilation.

Migration Steps

  1. 1
    If you were using `unstable_instant`, ensure it is only used within Server Components.
  2. 2
    If you rely on Turbopack compilation during your standard build, change your script from `pnpm build` to `pnpm build-all`.

Release Summary

This release introduces instant serving for cached navigations and enforces the use of `unstable_instant` only in Server Components. Several core fixes address worker compatibility, suspense boundaries, and server patching behavior.

Need More Details?

View the full release notes and all changes for Next.js v16.2.0-canary.62.

View Full Changelog