⚡️ Next.js just deleted 90% of your dev server's memory usage

Brought to you by

Hey guys,

Welcome to another edition of Import React by Cosden Solutions!

Next.js just shipped its biggest release since 16.0 — dev server memory down as much as 90%, builds up to 5.5x faster. A Reddit thread is quietly asking whether half of what React Server Components do is solving a problem nobody actually had. And there's a Playwright trick for catching a memory leak in your SPA before a customer does it for you.

Three days in Berlin, three concurrent stages, and 85 sessions built for React Native developers shipping production-grade, high-performance cross-platform apps with the New Architecture. Learn from the people building it — engineers from Meta, Amazon, Shopify, Expo, and Callstack — then take it further at hands-on workshops, roundtables, and a leadership summit for staff and principal engineers. One ticket unlocks it all: 8 concurrent dev events, including agentic codingCon and more! [sponsored]

See the full lineup and reserve your spot →

The headline number: up to 90% less memory in next dev for long sessions, thanks to disk caching plus a new eviction system. Builds get faster too — some projects are seeing 5.5x faster CI builds from that same disk-cache work. Under load, App Router SSR now handles 22% more requests after swapping web streams for native Node.js streams. There's also an experimental Rust port of the React Compiler (34–46% faster dev-to-ready-page times), TypeScript 7 support in next build, and a new Instant Navigations toolkit — Instant Insights, Partial Prefetching, and a Playwright helper for catching navigations that quietly stopped being instant. Full rundown here.

A developer working through the long-term tradeoffs of React Server Components posted a simple, needling question on r/reactjs: outside SEO and first-load speed, what has RSC actually solved for people running real, authenticated apps? The replies split fast. One camp calls it the most powerful architecture React has shipped and an inevitable direction for the server-client web. The other says if your app needs RSC, that's a sign you shouldn't be reaching for React at all — citing lost client-side caching, a network round-trip on every route change, and a level of internal complexity (useEffect vs. useLayoutEffect vs. useInsertionEffect) that's hard to justify for a small slice of real use cases. Read the thread and pick a side.

A static analysis of 500 popular React, Vue, and Angular repos found 86% left a listener, timer, or subscription registered and never cleaned it up — the kind of leak that's invisible until someone leaves a tab open for a few hours and the app crawls. Backend teams have soak-tested for this for years; frontend teams mostly don't. The fix: a Playwright test that loops a user flow a few hundred times inside one browser context, fakes the clock so an hour of polling compresses into minutes, and asserts the DOM node and listener counts come back to baseline. The full writeup, plus a ready-made fixture, walks through exactly where the tricky parts are — hint: you garbage-collect twice, not once.

Crop, resize, filters, draw, text, shapes, stickers, frames — and an optional AI Assistant for chat-based edits — all wrapped as a single React component with a real live demo. It's brand new (v1.0.0 shipped this month) and still tiny by star count, but the API is clean: pass an image, get a dataUrl back on save, and toggle any tool on or off through props. Try the live demo before deciding whether it earns a spot in your stack.

1,350 employees at frontier AI labs signed a public statement asking the U.S. government to help coordinate an internationally-paced approach to automating AI research. Signatories span Anthropic, OpenAI, Google DeepMind, and Meta AI, including Dario Amodei, Ilya Sutskever, and Jared Kaplan — the ask is for shared technical and governance tools to slow frontier progress deliberately, not a unilateral pause by any one lab.

Cloudflare thinks your coding agent needs a computer, not a container. Their new open-source @cloudflare/computer package gives every agent a shared, durable filesystem and lets it pick between a fast isolate or a full Linux container depending on the task — file edits and git operations run cheap, npm install and native binaries fall back to a container automatically.

Nearly half the benchmarks the AI field relies on may no longer mean much. A systematic study of 60 widely-used LLM benchmarks found 29 have saturated — top models are statistically indistinguishable on them. The uncomfortable finding: private test sets, harder formats, and multilingual scope don't protect against this once you control for how old a benchmark is. Age and test-set size explain almost all of it.

DeepSeek released the full version of V4-Flash, and it beats its own larger V4-Pro (Preview) model on agentic coding benchmarks despite a far smaller activated parameter count — landing broadly competitive with GLM-5.2 and Claude Opus 4.8 on the same tests.

That's it for this week. See you next Thursday.