Course contentsShow
← React
Lesson 697 of 2,39618. When NOT to Use useEffectFree lesson

The Dependency Array for Computation

useMemo dependencies should include all values used in the computation. Missing deps cause stale results; extra deps waste memoization.

The Dependency Array for Computation

In this lesson: You'll learn how to correctly specify dependencies for useMemo so your memoized computations stay accurate and efficient.


When you use useMemo to optimize an expensive computation, you must tell React which values that computation depends on. This is what the dependency array does — it lists every variable, prop, or state value your computation function reads.

How It Works

const result = useMemo(() => {
  return expensiveCalculation(value1, value2);
}, [value1, value2]); // Dependencies listed here

React checks the dependency array on every render. If value1 or value2 changed, it re-runs the computation. If they're the same as last render, it returns the cached result.

The Two Critical Mistakes

Missing dependencies cause stale results:

// ❌ BAD: missing `filter` from deps
const filtered = useMemo(() => {
  return items.filter(item => item.type === filter);
}, [items]); // filter is missing!

When filter changes, the computation doesn't re-run. You get outdated results using the old filter value.

Extra dependencies waste memoization:

// ❌ BAD: unrelated `userId` in deps
const total = useMemo(() => {
  return prices.reduce((sum, p) => sum + p, 0);
}, [prices, userId]); // userId is irrelevant

When userId changes, React re-runs the computation unnecessarily, even though total doesn't use userId at all.

The Rule

Include every value your computation reads — no more, no less. Think of dependencies as "ingredients" for your calculation: if you use it, list it.

Key Takeaway: The useMemo dependency array must include all values used in the computation. Missing dependencies create stale bugs; unnecessary dependencies defeat memoization. List exactly what you read.