0
Challenge · 34Hooks & Effects

useCallback

Performanceused in ~70% of apps

Every render rebuilds your functions from scratch, so each one is a brand-new reference. That fresh reference quietly breaks a memo'd child (#32) and re-fires a useEffect that depends on it. useCallback freezes a function's identity so those reference checks stay true.

Core idea. useCallback(fn, deps) caches a function definition between renders, handing you back the SAME function reference until a dependency changes. It is literally useMemo specialized for functions — useMemo(() => fn, deps) — and it stabilizes identity, nothing else.
Playground, this isn't a screenshot
<Parent/>rendered 1×
passingonClick = fn #1() => {}
memo(<Child/>)rendered 1×
const Child = memo(function Child({ onClick }) {…})
received onClickfn #1

Not wrapped. Click Re-render parent — a new function is created every render, so fn #ticks up and the memo'd child re-renders every single time. A fresh reference defeats memo.

↑ play a little first, then dig in