React.memo usage - Step-by-Step Execution

Concept Flow - React.memo usage

Component receives props

↓

React.memo compares new props

↓

Skip re-render

↓

Update DOM if needed

React.memo checks if props changed. If not, it skips re-render to save work.

Execution Sample

React

const MyComponent = React.memo(({ count }) => {
  console.log('Rendered:', count);
  return <div>{count}</div>;
});

<MyComponent count={1} />
<MyComponent count={1} />
<MyComponent count={2} />

This code shows React.memo preventing re-render when props stay the same.

Execution Table

Step	Props Received	Props Compared	Render Occurs?	Console Output
1	{ count: 1 }	No previous props	Yes	Rendered: 1
2	{ count: 1 }	Compare with { count: 1 }	No
3	{ count: 2 }	Compare with { count: 1 }	Yes	Rendered: 2

💡 At step 2, props are equal so React.memo skips re-render.

Variable Tracker

Variable	Start	After 1	After 2	After 3
props.count	undefined	1	1	2
rendered	false	true	false	true

Key Moments - 2 Insights

Why does the component not re-render at step 2 even though it is called again?

Because React.memo compares the new props { count: 1 } with previous props { count: 1 } and finds them equal, so it skips re-rendering as shown in execution_table row 2.

What happens if the props change, like at step 3?

React.memo detects the changed props { count: 2 } differ from previous { count: 1 }, so it allows the component to re-render, as shown in execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the console output at step 2?

A No output

B "Rendered: 2"

C "Rendered: 1"

D Error

💡 Hint

Check the 'Console Output' column for step 2 in the execution_table.

At which step does React.memo allow the component to re-render?

A Step 1

B Step 2

C Step 3

D None

💡 Hint

Look at the 'Render Occurs?' column in execution_table for steps where it says 'Yes'.

If the props never change, what will React.memo do on repeated renders?

A Always re-render the component

B Skip re-render to improve performance

C Throw an error

D Reset component state

💡 Hint

Refer to the concept_flow and execution_table where React.memo skips re-render when props are equal.

Concept Snapshot

React.memo is a function that wraps a component.
It compares new props with previous props.
If props are equal, it skips re-rendering.
This improves performance by avoiding unnecessary updates.
Use it for functional components that render the same output for same props.

Full Transcript

React.memo is a tool to optimize React functional components. When a component wrapped in React.memo receives props, React compares the new props with the previous ones. If they are the same, React.memo prevents the component from re-rendering, saving time and resources. In the example, the component renders at step 1 because it has no previous props. At step 2, the props are the same, so React.memo skips rendering. At step 3, the props change, so React.memo allows the component to render again. This behavior helps keep apps fast by avoiding unnecessary work.

Practice

1.

What is the main purpose of React.memo in React?

easy

A. To manage state inside a functional component

B. To convert a functional component into a class component

C. To prevent unnecessary re-rendering of a functional component when its props have not changed

D. To fetch data from an API automatically

Solution

1. Step 1: Understand React.memo's role

   React.memo is a higher-order component that wraps a functional component to optimize rendering.

2. Step 2: Identify its effect on rendering

   It skips re-rendering the component if the props are the same as the previous render.

3. Final Answer:

   To prevent unnecessary re-rendering of a functional component when its props have not changed -> Option C

4. Quick Check:

   React.memo optimizes rendering = A [OK]

Hint: React.memo skips re-render if props unchanged [OK]

Common Mistakes:

• Thinking React.memo manages state
• Confusing React.memo with class components
• Assuming React.memo fetches data

2.

Which of the following is the correct syntax to wrap a functional component MyComponent with React.memo?

easy

A. const MemoizedComponent = React.memo(MyComponent);

B. const MemoizedComponent = React.memo => MyComponent();

C. const MemoizedComponent = React.memo(MyComponent());

D. const MemoizedComponent = React.memo{MyComponent};

Solution

1. Step 1: Recall React.memo usage syntax

   React.memo is a function that takes a component and returns a memoized version.

2. Step 2: Check each option's syntax

   const MemoizedComponent = React.memo(MyComponent); correctly calls React.memo with the component reference without invoking it.

3. Final Answer:

   const MemoizedComponent = React.memo(MyComponent); -> Option A

4. Quick Check:

   React.memo(Component) syntax = D [OK]

Hint: React.memo takes component, no parentheses after component name [OK]

Common Mistakes:

• Calling component inside React.memo (using parentheses)
• Using arrow function syntax incorrectly
• Using braces instead of parentheses

3.

Consider this code snippet:

const MyComponent = React.memo(({ count }) => {
  console.log('Rendered');
  return <div>Count: {count}</div>;
});

function App() {
  const [count, setCount] = React.useState(0);
  const [text, setText] = React.useState('');

  return (
    <>
      <MyComponent count={count} />
      <input value={text} onChange={e => setText(e.target.value)} />
    </>
  );
}

What will be logged to the console when the user types in the input box?

medium

A. 'Rendered' logs only once when the component mounts

B. 'Rendered' logs every time the input changes

C. 'Rendered' never logs

D. 'Rendered' logs only when count changes

Solution

1. Step 1: Understand React.memo behavior with props

   MyComponent is memoized and only re-renders if its props change. It receives count as prop.

2. Step 2: Analyze prop changes on input update

   Typing changes text state, causing App to re-render. However, the count prop remains unchanged (same primitive value), so React.memo skips re-rendering MyComponent.

3. Step 3: Check if console logs on input change

   Since count does not change, React.memo prevents re-render, so 'Rendered' logs only once on mount.

4. Final Answer:

   'Rendered' logs only once when the component mounts -> Option A

5. Quick Check:

   React.memo skips re-render if props unchanged = B [OK]

Hint: React.memo skips re-render if props unchanged, so no log on input [OK]

Common Mistakes:

• Assuming any parent state change triggers child re-render
• Ignoring React.memo's prop comparison
• Thinking console logs every input change

4.

Consider this usage of React.memo:

const MyComponent = React.memo(({ value }) => {
  return <div>Value: {value}</div>;
}, (prevProps, nextProps) => {
  return prevProps.value === nextProps.value;
});

Which of the following correctly describes this code?

medium

A. The component function should not be an arrow function

B. The custom comparison function should return false when props are equal

C. React.memo cannot accept a second argument

D. The custom comparison function returns true when props are equal, which prevents re-rendering correctly

Solution

1. Step 1: Understand React.memo's custom comparison function

   The second argument is a function that returns true if props are equal, meaning skip re-render.

2. Step 2: Analyze the provided function

   The function returns true when prevProps.value === nextProps.value, which is correct to skip re-render when props are equal.

3. Step 3: Confirm the correct description

   The custom comparison function returns true when props are equal, which prevents re-rendering correctly accurately describes that it returns true when props are equal, preventing re-rendering correctly.

4. Final Answer:

   The custom comparison function returns true when props are equal, which prevents re-rendering correctly -> Option D

5. Quick Check:

   Custom compare returns true to skip re-render = C [OK]

Hint: Custom compare returns true to skip re-render [OK]

Common Mistakes:

• Thinking custom compare should return false when props equal
• Believing React.memo can't take a second argument
• Confusing arrow function usage

5.

You have a component wrapped with React.memo that receives a prop data which is an object. You notice it re-renders every time the parent renders, even if data has the same content. How can you fix this?

hard

A. Convert data to a string before passing it as prop

B. Use a custom comparison function in React.memo to do a deep comparison of data

C. Wrap the parent component with React.memo instead

D. Use useState inside the child component to store data

Solution

1. Step 1: Understand why re-renders happen with object props

   Objects are compared by reference, so even if content is same, new object causes re-render.

2. Step 2: Use custom comparison function

   React.memo accepts a second argument to compare props deeply and prevent re-render if content is equal.

3. Step 3: Evaluate other options

   Converting to string is inefficient and error-prone; wrapping parent doesn't solve child re-render; useState inside child doesn't prevent re-render.

4. Final Answer:

   Use a custom comparison function in React.memo to do a deep comparison of data -> Option B

5. Quick Check:

   Deep compare object props with custom function = A [OK]

Hint: Use custom compare to deep check object props [OK]

Common Mistakes:

• Passing new object each render without memoization
• Ignoring object reference equality
• Trying to fix with useState inside child