react-compiler-rules

To enforce React Compiler render purity rules, remove manual memoization via useMemo, useCallback, or React.memo and let the compiler handle optimizations. You must also separate side-channel code into useEffect to pass CLI-gate lint checks.

Manual memoization breaks React Compiler purity because render functions must remain free of side effects. The compiler automatically handles performance optimizations, making useMemo, useCallback, and React.memo unnecessary and prohibited under strict lint rules.

To separate side-channel animations from React render, move anime.js and PixiJS logic into useEffect using useAnime or usePixiApp hooks. This keeps render functions pure and ensures side-channel code only runs within effects.

Yes, React Compiler works with Jotai by treating hooks used in render as pure subscribers. You must avoid using Jotai hooks to drive render mutations, ensuring render functions remain pure and predictable under compiler optimization.

When lint gates detect render purity violations, they fail the code audit. This prevents merging improper memoization or unsafe side-channel render patterns, enforcing strict alignment with React Compiler rules across dean-stack projects.

No, you cannot use React.memo when the React Compiler is enabled. Manual memoization is prohibited because the compiler automatically handles performance optimizations, requiring you to remove React.memo to maintain render purity.