Post

Next.js
@nextjs.org

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 ↓

Next.js
@nextjs.org

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.

0 reposts11 likes

Next.js
@nextjs.org

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.

Next.js
@nextjs.org

TypeScript 7 is a 10x faster native port of the compiler, and πš—πšŽπš‘πš πš‹πšžπš’πš•πš now uses it for type checking. Install it with πš—πš™πš– πš’πš—πšœπšπšŠπš•πš• -𝙳 πšπš’πš™πšŽπšœπšŒπš›πš’πš™πš@7.

Next.js
@nextjs.org

App Router rendering now uses native Node.js streams end-to-end, instead of converting to and from web streams on each request. With that overhead gone, apps handle up to 22% more requests under load in our benchmarks.

Next.js
@nextjs.org

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.