Preventing Fetch on Every Render
You'll learn how to avoid the dreaded infinite loop when fetching data in useEffect by using a stable dependency array.
The Problem: Infinite Fetch Loops
When you fetch data based on changing props or state, you might accidentally create an infinite loop. This happens when your effect's dependency array includes unstable references—values that are recreated on every render, triggering the effect again and again.
Here's the classic mistake:
function UserProfile({ userId }) {
const [user, setUser] = useState(null);
useEffect(() => {
fetch(`/api/users/${userId}`)
.then(res => res.json())
.then(data => setUser(data));
}, [userId]); // ✅ Stable primitive value
return <div>{user?.name}</div>;
}
This works because userId is a primitive (number/string). But watch what happens with objects:
function UserProfile({ filters }) { // filters = { role: 'admin' }
const [users, setUsers] = useState([]);
useEffect(() => {
fetch(`/api/users?role=${filters.role}`)
.then(res => res.json())
.then(data => setUsers(data));
}, [filters]); // ⚠️ INFINITE LOOP!
return <div>...</div>;
}
Why? The parent creates a new filters object on every render. New object → effect runs → setUsers triggers re-render → parent re-renders → new filters object → repeat forever!
The Solution: Depend on Stable Values
Instead of depending on the object, depend on its primitive properties:
useEffect(() => {
fetch(`/api/users?role=${filters.role}`)
.then(res => res.json())
.then(data => setUsers(data));
}, [filters.role]); // ✅ Stable primitive
Now the effect only runs when filters.role actually changes value, not when the object reference changes.
Key Takeaway: Always include primitive values or stable references in your dependency array—objects and arrays created during render will cause infinite loops.