Missing Memoization on Complex Dependencies
You'll learn when to use useMemo to stabilize object and array dependencies so your effects don't run on every render.
The Problem: New References Every Render
When you pass an object or array as a dependency to useEffect, React compares it by reference, not by content. If you create a new object or array during render—even with identical values—React sees it as a different dependency and re-runs your effect.
function SearchResults({ userId }) {
const filters = { status: 'active', userId }; // ⚠️ New object every render!
useEffect(() => {
fetchData(filters);
}, [filters]); // Runs every single render
}
Even though filters might have the same values, it's a new object each render, causing an infinite loop if fetchData triggers a state update.
The Solution: useMemo for Stable References
Wrap complex dependencies in useMemo to preserve the same reference across renders when the values inside haven't changed:
function SearchResults({ userId }) {
const filters = useMemo(
() => ({ status: 'active', userId }),
[userId] // Only recreate when userId changes
);
useEffect(() => {
fetchData(filters);
}, [filters]); // Now stable unless userId changes
}
When to Apply This
Use useMemo for objects or arrays in dependencies when:
- They're created during render
- Their contents depend on props/state
- The effect would otherwise run too often
Key Takeaway: Objects and arrays in dependency arrays need useMemo to maintain stable references, preventing unnecessary effect re-runs caused by new references with identical content.