Course contentsShow
← React
Lesson 849 of 2,39622. Context PerformanceFree lesson

The Classic {{ user, setUser }} Trap

Inline object literals in Provider value prop create new references on every parent render, causing cascading re-renders.

The Classic {{ user, setUser }} Trap

You'll learn why passing an inline object to Context Provider causes every consumer to re-render unnecessarily.

The Problem

When you write a Context Provider like this:

<UserContext.Provider value={{ user, setUser }}>
  {children}
</UserContext.Provider>

You're creating a new object on every render. Even if user and setUser haven't changed, JavaScript sees {{ user, setUser }} as a fresh object each time. React compares the old value to the new value by reference, sees they're different objects, and tells every consumer to re-render.

The Trap in Action

function UserProvider({ children }) {
  const [user, setUser] = useState(null);

  // 🚨 NEW OBJECT EVERY RENDER
  return (
    <UserContext.Provider value={{ user, setUser }}>
      {children}
    </UserContext.Provider>
  );
}

Every time UserProvider re-renders (for any reason—even unrelated state changes), it creates a brand new { user, setUser } object. All consumers re-render, even though the actual user and setUser values are identical.

The Analogy

Imagine giving someone your business card. Even if your name and number are the same, handing them a different physical card each time makes them think something changed. React treats object references the same way.

Key Takeaway: Never pass inline object literals to value in Context Providers—you're forcing every consumer to re-render on every parent render, regardless of actual value changes.