you-might-not-need-a-memo

Avoid useMemo and React.memo when computations are cheap, dependencies change every render, or components receive always-new props, as this adds overhead without reducing re-renders.

Reduce unnecessary re-renders by applying structural fixes like the move state down and lift content up techniques to isolate changing state and prevent component tree re-rendering.

React.memo fails to prevent re-renders when components receive always-new prop references, causing referential churn that bypasses memoization checks and triggers rendering every time.

Fix derived state memoization by replacing useMemo with inline computation when the calculation is fast enough, removing the dependency tracking overhead and simplifying component logic.

You can automatically detect and refactor useMemo anti-patterns during code review by analyzing dependency stability and applying structural transformations across the affected component scope.

Structural approaches like lifting content up require refactoring component hierarchy and moving state boundaries, which can complicate prop passing and may not suit deeply nested component trees.