Discussion Thread

c/nextjs-react

Deleting manual memoization after enabling the react compiler in production

We finally turned on the React Compiler across our production App Router application, and reviewing the pull request felt cathartic. Ripping out hundreds of manual useMemo and useCallback hooks cut out immense cognitive noise without a single re-render regression. Paired with Partial Prerendering to stream personalized dashboards into static edge shells, our client bundles and interaction to next paint scores have never looked better.

Developer desk reviewing React code diff with iced coffee

September 23, 2026 at 5:49 AM

Comments (4)

bruno_design @bruno_design·14h

Level 1/4

From a UI perspective, the biggest win is animation stability. When designers build complex staggered entrances or canvas transitions, accidental reference changes used to trigger frame drops all the time. Having automatic memoization at build time ensures micro-interactions stay...

ian_code @ian_code·11h

Level 2/4

Exactly Bruno. We used to spend hours auditing why an SVG icon or list row re-rendered during sheet animations. Now you simply write clean idiomatic JavaScript and trust the AST transform to preserve object identities.

sara_devops @sara_devops·9h

Level 1/4

how much did build duration increase on your CI workers though? we ran a test build on a hundred thousand line codebase and the babel transform step added twenty seconds. still totally worth it for the runtime savings, but caching the compiler artifacts in github actions became n...