Why Objects in Dependencies Cause Re-runs
You'll learn: Why passing object literals or newly created objects to useEffect dependencies causes your effect to run on every render, even when the values inside haven't changed.
The Reference Equality Problem
JavaScript compares objects by reference, not by their contents. Every time you create a new object literal—even with identical properties—you get a new reference in memory. This is why {} !== {} always evaluates to true.
When React checks if dependencies have changed between renders, it uses Object.is() comparison (similar to ===). If you pass an object created during render as a dependency, React sees a new reference every single time, even if the object's contents are identical.
A Common Mistake
function UserProfile({ userId }) {
useEffect(() => {
console.log('Effect ran!');
// Fetch with filters...
}, [{ userId }]); // 🔴 NEW object every render!
return <div>Profile</div>;
}
Every render creates a fresh { userId } object. React sees a new reference and re-runs the effect, even if userId itself hasn't changed.
The Fix: Use Primitive Values
function UserProfile({ userId }) {
useEffect(() => {
console.log('Effect ran!');
// Fetch with filters...
}, [userId]); // ✅ Primitive value compared by value
return <div>Profile</div>;
}
Now the effect only runs when userId actually changes, because primitive values are compared by their value, not reference.
The Memory Analogy
Think of objects as houses. Even if two houses have identical floor plans, they're at different addresses. React checks the address (reference), not the furniture inside (values).
Key Takeaway: New object literals in the dependency array create new references every render, causing infinite re-runs. Always depend on primitive values or stable references (via useMemo or useCallback), never inline object literals.