useCallback hook in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the useCallback hook in React?

The useCallback hook is used to remember a function between renders. It helps avoid recreating functions unnecessarily, which can improve performance especially when passing functions to child components.

beginner

How do you use useCallback to memoize a function that depends on a state variable count?

You wrap the function with <code>useCallback</code> and list <code>count</code> in the dependency array like this: <br><pre>const memoizedFn = useCallback(() =&gt; { console.log(count); }, [count]);</pre>

intermediate

What happens if you pass an empty dependency array [] to useCallback?

The function is created once and never recreated again during the component's lifetime. It always uses the initial values from when it was created.

intermediate

Why might you want to use useCallback when passing functions to child components?

Because React compares props to decide if a child should update. If you pass a new function every time, the child thinks props changed and re-renders. useCallback keeps the same function reference if dependencies don’t change, preventing unnecessary child re-renders.

advanced

Can useCallback improve performance in all cases? Why or why not?

No. Using useCallback adds some overhead to remember the function. It helps mainly when passing functions to memoized children or expensive computations. For simple cases, it might not improve and can even slow down slightly.

What does useCallback return?

A A memoized version of the callback function

B A new component

C A state variable

D A side effect

useCallback returns a memoized function that only changes if its dependencies change.

Which of these is a correct way to use useCallback?

A useCallback(() => { doSomething(); })

B useCallback(doSomething(), [])

C useCallback(doSomething)

D useCallback(() => { doSomething(); }, [dependency])

You pass a function and a dependency array to useCallback. Option D shows the correct syntax.

What happens if you omit the dependency array in useCallback?

A The function is memoized forever

B The function is recreated on every render

C React throws an error

D The function is created once and never updated

Without dependencies, useCallback recreates the function every render, defeating its purpose.

Why is it useful to memoize functions passed as props to child components?

A To make the function run faster

B To increase the size of the app

C To prevent unnecessary child re-renders

D To change the child component's state

Memoizing functions keeps the same reference, so children don’t re-render if props don’t change.

Which hook is often used together with useCallback to optimize child components?

A React.memo

B useMemo

C useState

D useEffect

React.memo memoizes components and works well with useCallback to avoid unnecessary renders.

Explain how useCallback helps improve performance in React applications.

Think about how React decides to re-render children when props change.

Describe the correct way to use useCallback and what happens if dependencies change or stay the same.

Focus on the role of the dependency array in <code>useCallback</code>.

Practice

1. What is the main purpose of the useCallback hook in React?

easy

A. To memoize a function so it doesn't get recreated on every render unless dependencies change

B. To store a value that persists between renders

C. To fetch data from an API asynchronously

D. To create a new state variable

Solution

1. Step 1: Understand what useCallback does

   useCallback returns a memoized version of a function that only changes if its dependencies change.

2. Step 2: Compare options with this behavior

   Only To memoize a function so it doesn't get recreated on every render unless dependencies change describes memoizing a function to avoid recreating it unnecessarily.

3. Final Answer:

   To memoize a function so it doesn't get recreated on every render unless dependencies change -> Option A

4. Quick Check:

   useCallback = memoize function [OK]

Hint: Remember: useCallback memoizes functions to keep them stable [OK]

Common Mistakes:

• Confusing useCallback with useState
• Thinking useCallback stores values instead of functions
• Assuming useCallback fetches data

2. Which of the following is the correct syntax to use useCallback in a React functional component?

easy

A. const memoizedFn = useCallback(doSomething(), [dependency]);

B. const memoizedFn = useCallback(() => { doSomething(); });

C. const memoizedFn = useCallback(() => { doSomething(); }, [dependency]);

D. const memoizedFn = useCallback(doSomething, dependency);

Solution

1. Step 1: Recall the correct useCallback signature

   The hook takes a function and an array of dependencies: useCallback(fn, [deps]).

2. Step 2: Analyze each option

   const memoizedFn = useCallback(() => { doSomething(); }, [dependency]); correctly passes an inline function and dependencies array. const memoizedFn = useCallback(() => { doSomething(); }); misses dependencies array. const memoizedFn = useCallback(doSomething(), [dependency]); calls doSomething() immediately, passing its return value instead of the function. const memoizedFn = useCallback(doSomething, dependency); passes dependency without array brackets, invalid.

3. Final Answer:

   const memoizedFn = useCallback(() => { doSomething(); }, [dependency]); -> Option C

4. Quick Check:

   useCallback(fn, [deps]) [OK]

Hint: useCallback needs a function and an array of dependencies [OK]

Common Mistakes:

• Omitting the dependencies array
• Passing dependencies without array brackets
• Passing function call instead of function reference

3. Consider this React component code:

const MyComponent = () => {
  const [count, setCount] = React.useState(0);
  const increment = React.useCallback(() => {
    setCount(count + 1);
  }, [count]);
  return <button onClick={increment}>Increment</button>;
};

What happens when the button is clicked multiple times quickly?

medium

A. The count increments correctly each time

B. The code throws an error because of missing dependencies

C. The count increments only once and then stops

D. The count increments but may lag behind due to stale closure

Solution

1. Step 1: Understand the closure inside useCallback

   The increment function uses count from its dependencies. Because count is in the dependency array, the function updates when count changes, but rapid clicks may use a stale value.

2. Step 2: Analyze behavior on quick clicks

   Rapid clicks may cause the function to use an outdated count value due to closure, causing increments to lag behind actual clicks.

3. Final Answer:

   The count increments but may lag behind due to stale closure -> Option D

4. Quick Check:

   useCallback with state dependency can cause stale closures [OK]

Hint: State in useCallback can be stale if updated rapidly [OK]

Common Mistakes:

• Assuming count always updates instantly
• Ignoring closure behavior in hooks
• Thinking useCallback prevents all stale data issues

4. Identify the bug in this code using useCallback:

const MyComponent = () => {
  const [value, setValue] = React.useState(0);
  const handleClick = React.useCallback(() => {
    setValue(value + 1);
  }, []);
  return <button onClick={handleClick}>Click</button>;
};

medium

A. Missing dependency value in the dependency array causes stale state updates

B. Using useCallback without dependencies causes infinite re-renders

C. setValue should not be called inside useCallback

D. The function should not be memoized with useCallback

Solution

1. Step 1: Check the dependency array of useCallback

   The callback uses value but the dependency array is empty, so the function never updates with new value.

2. Step 2: Understand the effect of missing dependencies

   Because value is missing, the callback uses the initial value forever, causing stale increments.

3. Final Answer:

   Missing dependency value in the dependency array causes stale state updates -> Option A

4. Quick Check:

   Dependencies must include all used variables [OK]

Hint: Always include all variables used inside useCallback in dependencies [OK]

Common Mistakes:

• Leaving dependency array empty when variables are used
• Thinking setState functions need dependencies
• Confusing useCallback with useMemo

5. You want to optimize a child component that receives a callback prop to avoid unnecessary re-renders. Which approach correctly uses useCallback to achieve this?

const Parent = () => {
  const [count, setCount] = React.useState(0);

  // Which is correct?
  const handleClick = ???

  return <Child onClick={handleClick} />;
};

hard

A. const handleClick = React.useCallback(() => setCount(count + 1), [count]);

B. const handleClick = React.useCallback(() => setCount(c => c + 1), []);

C. const handleClick = () => setCount(count + 1);

D. const handleClick = React.useCallback(() => setCount(count + 1));

Solution

1. Step 1: Understand the goal to avoid unnecessary re-renders

   We want handleClick to be stable and not change unless needed, so the child doesn't re-render unnecessarily.

2. Step 2: Analyze each option's dependency array and function

   const handleClick = React.useCallback(() => setCount(count + 1), [count]); depends on count, so it changes every time count changes, causing re-renders. const handleClick = React.useCallback(() => setCount(c => c + 1), []); uses functional update c => c + 1 and empty dependencies, so handleClick is stable. const handleClick = () => setCount(count + 1); recreates function every render. const handleClick = React.useCallback(() => setCount(count + 1)); misses dependencies array, which is invalid.

3. Final Answer:

   const handleClick = React.useCallback(() => setCount(c => c + 1), []); -> Option B

4. Quick Check:

   Stable callback with functional update and empty deps = const handleClick = React.useCallback(() => setCount(c => c + 1), []); [OK]

Hint: Use functional updates with empty deps to keep callback stable [OK]

Common Mistakes:

• Including state in dependencies causing new functions each render
• Not using functional updates when deps are empty
• Omitting dependency array causing bugs