Post

Next.js 16.3 is now available! • Up to 90% less memory in dev • Faster builds, type checking, and rendering • Better tooling for AI agents • Custom error boundaries • Instant Navigations for SPA-like responsiveness nextjs.org/blog/next-16-3 Here's what's new ↓

Long 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 sessions now use up to 90% less memory. Turbopack used to keep visited routes cached in memory. With disk caching and memory eviction on by default, it can now offload that cache to disk.

The disk cache that has sped up 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 since 16.1 now also works for 𝚗𝚎𝚡𝚝 𝚋𝚞𝚒𝚕𝚍. Turbopack can read existing entries from .𝚗𝚎𝚡𝚝/𝚌𝚊𝚌𝚑𝚎 across CI runs before compiling new changes. We've seen projects build up to 5.5x faster on the warm path.

TypeScript 7 is a 10x faster native port of the compiler, and 𝚗𝚎𝚡𝚝 𝚋𝚞𝚒𝚕𝚍 now uses it for type checking. Install it with 𝚗𝚙𝚖 𝚒𝚗𝚜𝚝𝚊𝚕𝚕 -𝙳 𝚝𝚢𝚙𝚎𝚜𝚌𝚛𝚒𝚙𝚝@7.

React error boundaries used to swallow 𝚗𝚘𝚝𝙵𝚘𝚞𝚗𝚍 and 𝚛𝚎𝚍𝚒𝚛𝚎𝚌𝚝, and could only reset client state. Now 𝚌𝚊𝚝𝚌𝚑𝙴𝚛𝚛𝚘𝚛 defines a custom boundary that lets those pass through, and 𝚛𝚎𝚝𝚛𝚢() re-renders Server Components within the boundary.

Turbopack now supports the Vite-compatible 𝚒𝚖𝚙𝚘𝚛𝚝.𝚖𝚎𝚝𝚊.𝚐𝚕𝚘𝚋 API for loading multiple modules from the file system. For a Server Component that reads local files, like a folder of Markdown posts, it also brings hot-module reloading.

Agents often code using outdated patterns from their training data. Now, 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 maintains an 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 block that points them to a local copy of the docs pinned to your app's version, ensuring they always use the latest best practices.