State and hooks in client components in NextJS - Step-by-Step Execution

Concept Flow - State and hooks in client components

Component Render Start

↓

useState Hook Called

↓

State Variable Initialized

↓

JSX Rendered with State Value

↓

User Clicks Button

↓

setState Called

↓

Component Re-renders

↓

Updated State Value Shown

↓

End

The component renders, initializes state with useState, shows it in JSX, then updates state on user action causing re-render with new state.

Execution Sample

NextJS

'use client';
import { useState } from 'react';

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

A button shows a count starting at 0 and increments by 1 each time it is clicked.

Execution Table

Step	Action	State Before	State Update	State After	Rendered Output
1	Component renders first time	count = undefined	useState(0) sets count to 0	count = 0	Button shows 'Count: 0'
2	User clicks button	count = 0	setCount(count + 1) called	count = 0	Button shows 'Count: 0'
3	Component re-renders	count = 1	No state change	count = 1	Button shows 'Count: 1'
4	User clicks button again	count = 1	setCount(count + 1) called	count = 1	Button shows 'Count: 1'
5	Component re-renders	count = 2	No state change	count = 2	Button shows 'Count: 2'
6	No more clicks	count = 2	No action	count = 2	Button shows 'Count: 2'

💡 Execution stops when user stops clicking; state remains stable and UI shows latest count.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	Final
count	undefined	0	1	2	2

Key Moments - 3 Insights

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

Calling setCount updates the state variable 'count', which tells React to re-render the component to show the new state value, as seen in steps 2 and 3 of the execution_table.

Why is the initial state value 0 and not undefined?

The useState hook initializes 'count' to 0 on the first render, as shown in step 1 where useState(0) sets count to 0.

Does the component re-render if setCount is not called?

No, the component only re-renders when state changes. Steps 3 and 5 show re-renders after state updates, but no re-render happens without setCount.

Visual Quiz - 3 Questions

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

A 1

B 0

C 2

D undefined

💡 Hint

Check the 'State After' column for step 2 in the execution_table.

At which step does the component first render with count equal to 2?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the 'Rendered Output' column and find when 'Count: 2' appears.

If the user never clicks the button, what will the final rendered output be?

A Count: 1

B Count: 0

C Count: undefined

D No output

💡 Hint

Refer to step 1 and step 6 in the execution_table for initial and final render states.

Concept Snapshot

useState hook creates a state variable and setter.
Initial state is set on first render.
Calling setter updates state and triggers re-render.
Component shows latest state in JSX.
User actions can call setter to change state.
Re-render updates UI with new state value.

Full Transcript

This example shows a Next.js client component using the useState hook to manage a count variable. Initially, the count is set to 0. The component renders a button displaying the current count. When the user clicks the button, the setCount function updates the count by adding 1. This triggers React to re-render the component, showing the updated count. The execution table traces each step: initial render, user clicks, state updates, and re-renders. The variable tracker shows how 'count' changes from undefined to 0, then increments with each click. Key moments clarify why re-renders happen and how initial state is set. The visual quiz tests understanding of state values at different steps and the effect of user interaction. This teaches how state and hooks work together to create interactive client components in Next.js.