Re-rendering behavior in React - Step-by-Step Execution

Concept Flow - Re-rendering behavior

Initial Render

↓

Component Renders JSX

↓

User Interaction or State Change

↓

setState Called

↓

React Schedules Re-render

↓

Component Re-renders with New State

↓

DOM Updates with Differences

↓

Render Complete

This flow shows how React renders a component initially, then re-renders it when state changes, updating the DOM efficiently.

Execution Sample

React

import React, { useState } from 'react';

function Counter() {
  const [count, setCount] = useState(0);
  return (
    <button onClick={() => setCount(count + 1)}>Count: {count}</button>
  );
}

export default Counter;

A simple button that shows a count and increases it by 1 each time you click.

Execution Table

Step	Trigger	State Before	Action	State After	What Re-renders	DOM Change
1	Initial render	count = 0	Render JSX	count = 0	Counter component	Button shows 'Count: 0'
2	User clicks button	count = 0	setCount(1)	count = 1	Counter component	Button updates to 'Count: 1'
3	User clicks button	count = 1	setCount(2)	count = 2	Counter component	Button updates to 'Count: 2'
4	User clicks button	count = 2	setCount(3)	count = 3	Counter component	Button updates to 'Count: 3'
5	No more clicks	count = 3	No action	count = 3	No re-render	DOM unchanged

💡 Execution stops when no further user interaction triggers state changes.

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
count	0	1	2	3	3

Key Moments - 3 Insights

Why does the component re-render when setCount is called?

Calling setCount changes the state value 'count', which tells React to re-render the component with the new state, as shown in steps 2-4 of the execution_table.

Does React re-render the whole page when state changes?

No, React only re-renders the component where state changed and updates the DOM efficiently, not the entire page. This is seen in the 'What Re-renders' and 'DOM Change' columns.

What happens if setCount is called with the same value as current state?

React will not re-render the component because the state did not actually change, so no DOM update occurs. This is implied in step 5 where no action means no re-render.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'count' after step 3?

A 2

B 1

C 3

D 0

💡 Hint

Check the 'State After' column in row with Step 3.

At which step does the DOM update to show 'Count: 1'?

A Step 1

B Step 2

C Step 3

D Step 5

💡 Hint

Look at the 'DOM Change' column for when the button text changes to 'Count: 1'.

If the user never clicks the button, how many times does the component re-render?

A 3 times

B 0 times

C 1 time

D Infinite times

💡 Hint

Refer to Step 1 and Step 5 in the execution_table about initial render and no further re-renders.

Concept Snapshot

React re-renders a component when its state changes.
Use useState to hold state.
Calling setState schedules a re-render.
Only the component with changed state re-renders.
DOM updates reflect new state efficiently.
No re-render if state value is unchanged.

Full Transcript

This visual execution shows how React components render and re-render. Initially, the Counter component renders with count 0. When the user clicks the button, setCount updates the state, triggering React to re-render the component with the new count. The DOM updates only the button text to show the new count. This process repeats with each click, increasing count and updating the display. If the state does not change, React skips re-rendering to optimize performance.

Practice

1. Which of the following causes a React component to re-render?

easy

A. When a variable inside the component function changes but state does not

B. When the component's state changes using a state setter like setState or useState setter

C. When the component's CSS styles change

D. When the browser window is resized

Solution

1. Step 1: Understand React's re-render triggers

   React re-renders a component when its state or props change, not just any variable or style change.

2. Step 2: Identify the correct trigger

   Using setState or the setter from useState updates state and triggers re-rendering.

3. Final Answer:

   When the component's state changes using a state setter like setState or useState setter -> Option B

4. Quick Check:

   State change triggers re-render = B [OK]

Hint: State or props change triggers re-rendering in React [OK]

Common Mistakes:

• Thinking local variable changes cause re-render
• Assuming style changes trigger re-render
• Believing window resize triggers component re-render

2. Which of the following is the correct way to update state and trigger a re-render in a React functional component?

easy

A. this.state.count = 5;

B. count = 5;

C. updateState(count = 5);

D. setCount(5);

Solution

1. Step 1: Recall state update syntax in functional components

   In React functional components, state is updated using the setter function returned by useState, e.g., setCount.

2. Step 2: Identify the correct syntax

   Direct assignment like this.state.count = 5 or count = 5 does not trigger re-render. Only calling setCount(5) updates state properly.

3. Final Answer:

   setCount(5); -> Option D

4. Quick Check:

   Use setter function to update state = C [OK]

Hint: Use setter from useState to update state, not direct assignment [OK]

Common Mistakes:

• Trying to assign state directly
• Using undefined functions like updateState
• Confusing class component syntax with functional

3. Consider this React functional component:

function Counter() {
  const [count, setCount] = React.useState(0);
  console.log('Render:', count);
  return (
    <button onClick={() => setCount(count + 1)}>Count: {count}</button>
  );
}

What will be logged to the console after clicking the button three times?

medium

A. Render: 0, Render: 1, Render: 2, Render: 3

B. Render: 0, Render: 1

C. Render: 3 only

D. Render: 1, Render: 2, Render: 3

Solution

1. Step 1: Understand initial render and state updates

   Initially, the component renders with count = 0 and logs 'Render: 0'. Each button click calls setCount(count + 1), updating state and causing re-render.

2. Step 2: Trace each click and render

   After first click, count becomes 1 and logs 'Render: 1'. Second click updates count to 2 and logs 'Render: 2'. Third click updates count to 3 and logs 'Render: 3'.

3. Final Answer:

   Render: 0, Render: 1, Render: 2, Render: 3 -> Option A

4. Quick Check:

   Each state update triggers render log = A [OK]

Hint: Each state update triggers a new render and console log [OK]

Common Mistakes:

• Ignoring initial render log
• Assuming only last render logs
• Thinking state updates batch without intermediate renders

4. Given this React component:

function Example() {
  const [value, setValue] = React.useState(0);
  function update() {
    value = value + 1;
  }
  return <button onClick={update}>Value: {value}</button>;
}

Why does clicking the button NOT update the displayed value?

medium

A. Because direct assignment to value does not update state or trigger re-render

B. Because the update function is not called on click

C. Because the initial state is zero and never changes

D. Because React does not allow state updates inside event handlers

Solution

1. Step 1: Identify how state updates trigger re-render

   React re-renders when state is updated via the setter function, not by direct variable assignment.

2. Step 2: Analyze the update function

   The function assigns value = value + 1 directly, which changes a local variable but does not update React state or cause re-render.

3. Final Answer:

   Because direct assignment to value does not update state or trigger re-render -> Option A

4. Quick Check:

   State must be updated via setter to re-render = A [OK]

Hint: Always use state setter to update state, not direct assignment [OK]

Common Mistakes:

• Thinking direct assignment updates state
• Assuming event handler is not called
• Believing React forbids state updates in handlers

5. You have a parent component passing a prop count to a child component. The child uses React.memo to avoid unnecessary re-renders. Which of these changes will cause the child to re-render?

hard

A. The parent re-renders but passes the same count value as before

B. A variable inside the child component function changes but state does not

C. The parent passes a new count value different from before

D. The parent changes an unrelated state but count stays the same

Solution

1. Step 1: Understand React.memo behavior

   React.memo prevents re-render if props are shallowly equal. If props change, it re-renders.

2. Step 2: Analyze each option

   A: Same count means props equal, no re-render.
   B: Local variable change does not update state or props, no re-render.
   C: Unrelated state change in parent does not affect child's props if count same.
   D: New count value means props changed, triggers re-render.

3. Final Answer:

   The parent passes a new count value different from before -> Option C

4. Quick Check:

   Prop change triggers React.memo re-render = D [OK]

Hint: React.memo re-renders only if props change shallowly [OK]

Common Mistakes:

• Thinking parent re-render always triggers child re-render
• Ignoring prop equality in React.memo
• Thinking local variable changes cause re-render