Primitive Values Don't Need Memoization
What you'll learn: Why numbers, strings, booleans, null, and undefined don't need useMemo when used as Context values.
The Core Idea
In JavaScript, primitive values (numbers, strings, booleans, null, undefined) are compared by value, not by reference. This means two primitives with the same content are always considered equal. When you pass a primitive to a Context Provider's value prop, React can correctly detect when nothing has changed—no useMemo needed.
Why This Matters
Remember how objects created inline (like {{ user, setUser }}) cause unnecessary re-renders? That's because objects are compared by reference—a new object is never equal to the previous one, even with identical contents.
Primitives work differently:
5 === 5 // always true
"hello" === "hello" // always true
true === true // always true
Each render producing the same primitive value won't trigger Context consumers to re-render, because React sees them as equal.
When You Can Skip useMemo
// ✅ No useMemo needed - primitive value
<ThemeContext.Provider value="dark">
// ✅ No useMemo needed - still a primitive
<CountContext.Provider value={count}>
// ✅ No useMemo needed - boolean
<LoadingContext.Provider value={isLoading}>
This doesn't mean primitives can't cause re-renders—if the primitive value changes (like count going from 5 to 6), consumers should re-render. The point is you won't get unnecessary re-renders from the same value.
Key Takeaway: Primitive values (numbers, strings, booleans, null, undefined) are compared by value in JavaScript, so passing them to Context never causes the "new reference" problem that requires useMemo. Save useMemo for objects and arrays.