Object and Array Dependencies: Equality by Reference
What you'll learn: Why putting objects or arrays in useEffect's dependency array causes your effect to run on every single render, even when the data "looks" the same.
The Core Problem
When React checks if a dependency has changed, it uses referential equality — literally asking "is this the exact same thing in memory?" For primitives like numbers or strings, this works intuitively. But objects and arrays are compared by reference, not by their contents.
Every time your component renders, any object or array you create is a brand new object in memory, even if it contains identical values.
// This effect runs on EVERY render
useEffect(() => {
console.log('Effect ran!');
}, [{ name: 'Alice' }]); // New object every render!
// So does this one
useEffect(() => {
console.log('Effect ran again!');
}, [[1, 2, 3]]); // New array every render!
The Analogy
Imagine two identical houses at different addresses. When React asks "is this the same house?" it's checking the address (reference), not whether the rooms inside look identical. Two houses at different addresses are different houses, even if they're built exactly the same way.
Why This Matters
If you define an object or array inline in your dependency array, or create it fresh during render, React sees a different reference every time. Your effect will run on every render, defeating the purpose of the dependency array entirely.
Key Takeaway: Objects and arrays are compared by reference, not content. A newly created object or array in your dependency array will cause your effect to run on every render, even if the values inside are identical.