Read real React Compiler 1.0 output line by line, see why components stop re-rendering without React.memo, hand-compile a component yourself, and learn the cases it can't fix: mutation, values from outside React, rule violations it silently skips, and work that's slow even when memoized. Ends with a safe rollout plan.
React's rendering model is simple: when a component's state changes, React calls it again, and every component it renders, all the way down. Most of those re-renders produce exactly the same output as last time. They're wasted work, and in a big tree they're what makes typing lag and clicks feel slow.
For years the answer was manual memoization:
React.memo(Component) to skip a child when its props are unchanged,useMemo to keep an expensive value between renders,useCallback to keep a function's identity stable, so a memoized child doesn't see a "new" prop.It works, but it's fragile:
style={{ margin: 4 }} or onClick={() => ...} to a memo child and it re-renders every time anyway.The React Compiler automates this. It's a build-time tool (a Babel plugin, with integrations for Next.js, Vite and others) that analyzes each component and hook and rewrites it to cache values, callbacks and JSX by their inputs. Version 1.0 has been stable since October 2025, and it works with React 17, 18 and 19.
What it is:
What it isn't: