0
Challenge · 30Hooks & Effects

Context Optimization

Coreused in ~60% of apps

Context is easy to add and easy to make slow: one careless line in your Provider can re-render every consumer on the page, every render. Knowing why — and the two fixes — is a classic mid-level interview filter.

Core idea. Every component that reads a context re-renders whenever the Provider's value changes by reference (Object.is). An inline value={{...}} is a new object every render, so all consumers re-render even when nothing meaningful changed — fix it by memoizing the value or splitting state and dispatch into separate contexts.
Playground, this isn't a screenshot

value={{ user, theme, dispatch }}

<AppCtx.Provider value={…}>value:#1

Provider renders: 1× · new ref every render

1×
<UserBadge />
reads user
1×
<ThemeToggle />
reads theme
1×
<LogoutButton />
only calls dispatch
Pick a strategy, then press a button below and watch which consumers re-render.
re-rendered (red flash) render count
↑ play a little first, then dig in