Next.js 16's cacheComponents hides the pages you leave with React Activity instead of unmounting them. Following a three.js canvas that went blank after a back navigation, I read the router, React, and react-three-fiber source and reproduced it in a browser.
Every odd rule of React's cache() falls straight out of a ~30-line implementation. We trace the dispatcher, getCacheForType, and the WeakMap/Map tree at the source level to see exactly how request-scoped memoization works.
Build-time transformations, cache key serialization, ResumeDataCache, cacheHandler, and Cache Components - everything created by a single 'use cache' line
Module boundaries created by a single line of 'use client', build-time transformations, Flight serialization, and performance implications
The uncomfortable truth benchmarks reveal
The questions React Foundation must answer
What happens behind a single line of "use server"?
What happens when React wraps the View Transition API
A deep exploration of how React Compiler analyzes code and what it produces, from pipeline to final output.
Exploring the four cache layers of the Next.js App Router
Why you shouldn't call setState in Effects and what alternatives exist
An RFC from 3 years ago finally sees the light of day
CVE-2025-55182, CVE-2025-55184, CVE-2025-55183, and the React hidden inside Next.js
Thank you for your interest. ๐๐ปโโ๏ธ
The name may change, or it may disappear entirely, depending on how things go
