Event handlers in client components in NextJS - Step-by-Step Execution

Concept Flow - Event handlers in client components

User action: click/button press

↓

Event handler function triggered

↓

State update or side effect

↓

Component re-renders if state changed

↓

DOM updates to reflect new state

↓

User sees updated UI

When a user interacts with a component, the event handler runs, updates state or triggers effects, causing the component to re-render and update the UI.

Execution Sample

NextJS

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

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

A button that counts how many times it is clicked by updating state on each click.

Execution Table

Step	User Action	State Before	Event Handler Action	State After	Component Re-render	UI Output
1	Page loads	count = 0	No event	count = 0	Initial render	Button shows 'Clicked 0 times'
2	User clicks button	count = 0	setCount(0 + 1)	count = 1	Re-render	Button shows 'Clicked 1 time'
3	User clicks button	count = 1	setCount(1 + 1)	count = 2	Re-render	Button shows 'Clicked 2 times'
4	User clicks button	count = 2	setCount(2 + 1)	count = 3	Re-render	Button shows 'Clicked 3 times'

💡 No more user clicks, so no further state changes or re-renders.

Variable Tracker

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

Key Moments - 3 Insights

Why does the UI update after clicking the button?

Because the event handler calls setCount which updates the state, triggering React to re-render the component with the new count value (see execution_table steps 2-4).

What happens if the event handler does not update state?

The component will not re-render and the UI will not change, as React only updates the DOM when state or props change (see execution_table step 1).

Can the event handler run without user interaction?

No, event handlers run only in response to user actions like clicks or key presses (see execution_table step 1 where no event means no handler run).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'count' after the second click?

A 1

B 2

C 3

D 0

💡 Hint

Check the 'State After' column at step 3 in the execution_table.

At which step does the component first re-render?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Component Re-render' column; the first 'Re-render' (not initial) happens at step 2.

If the event handler did not call setCount, what would the UI show after clicks?

A The button would disappear

B The count would increase normally

C The count would stay at 0

D An error would occur

💡 Hint

Refer to key_moments where state update triggers UI change.

Concept Snapshot

Event handlers in client components:
- Attach functions to UI events like clicks
- Functions run on user action
- Use state setters (e.g., setCount) to update state
- State change triggers component re-render
- UI updates to reflect new state
- Always client-side for interactivity

Full Transcript

This example shows how event handlers work in Next.js client components. When the user clicks the button, the onClick handler runs. It calls setCount to increase the count state by one. React then re-renders the component with the updated count. The button text updates to show the new count. Without state change, the UI would not update. Event handlers only run on user actions like clicks. This flow ensures interactive UI updates smoothly.

Practice

1. In Next.js client components, how do you correctly attach a click event handler to a button?

easy

A. Use onClick="handleClick()" as a string.

B. Use onclick="handleClick()" as a string.

C. Use click={handleClick} without 'on'.

D. Use onClick={handleClick} with a function reference.

Solution

1. Step 1: Understand React event handler syntax

   React and Next.js use camelCase event names and expect a function reference, not a string.

2. Step 2: Identify correct JSX usage

   The correct way is onClick={handleClick}, passing the function directly.

3. Final Answer:

   Use onClick={handleClick} with a function reference. -> Option D

4. Quick Check:

   React event handlers use camelCase and function references [OK]

Hint: Use camelCase and pass function, not string, for events [OK]

Common Mistakes:

• Using lowercase 'onclick' attribute as string
• Passing event handler as a string instead of function
• Omitting 'on' prefix in event name

2. Which of the following is the correct syntax to define an arrow function with block body for a click event handler in a Next.js client component?

easy

A. const handleClick = () => { alert('Clicked!'); }

B. function handleClick() { alert('Clicked!'); }

C. const handleClick = alert('Clicked!');

D. const handleClick = () => alert('Clicked!');

Solution

1. Step 1: Check arrow function syntax

   const handleClick = () => { alert('Clicked!'); } correctly defines an arrow function with braces and a statement inside.

2. Step 2: Compare other options

   const handleClick = () => alert('Clicked!'); uses concise arrow function syntax without braces; function handleClick() { alert('Clicked!'); } uses traditional function declaration; const handleClick = alert('Clicked!'); calls alert immediately, not defining a function.

3. Final Answer:

   const handleClick = () => { alert('Clicked!'); } -> Option A

4. Quick Check:

   Arrow function with braces and alert call is correct [OK]

Hint: Use arrow functions with braces for event handlers [OK]

Common Mistakes:

• Calling alert immediately instead of wrapping in function
• Missing braces for multiple statements
• Using old function syntax unnecessarily

3. What will be the output when the button is clicked in this Next.js client component?

import { useState } from 'react';

export default function Counter() {
  const [count, setCount] = useState(0);
  const increment = () => setCount(count + 1);
  return (
    Clicked {count} times
  );
}

medium

A. Button text stays 'Clicked 0 times' even after clicks.

B. Button text updates to 'Clicked 1 times' on first click and increments thereafter.

C. Button text shows 'Clicked NaN times' after click.

D. Button causes a runtime error on click.

Solution

1. Step 1: Understand useState and event handler

   The state variable 'count' starts at 0 and increments by 1 on each click via setCount.

2. Step 2: Predict UI update on click

   Clicking the button calls increment, updating count and re-rendering button text with new count.

3. Final Answer:

   Button text updates to 'Clicked 1 times' on first click and increments thereafter. -> Option B

4. Quick Check:

   useState updates UI dynamically on event [OK]

Hint: useState updates state and UI on event triggers [OK]

Common Mistakes:

• Not using useState to update UI
• Calling setCount incorrectly
• Expecting static text without re-render

4. Identify the error in this Next.js client component code snippet:

import { useState } from 'react';

export default function Toggle() {
  const [on, setOn] = useState(false);
  function toggle() {
    setOn(!on);
  }
  return (
    {on ? 'ON' : 'OFF'}
  );
}

medium

A. useState initial value should be a string, not boolean.

B. The toggle function should use setOn(prev => !prev) instead of setOn(!on).

C. The event handler attribute should be 'onClick' with capital C.

D. The button element must be wrapped in a fragment.

Solution

1. Step 1: Check event handler attribute spelling

   React and Next.js require camelCase event names, so 'onclick' is incorrect; it must be 'onClick'.

2. Step 2: Validate other code parts

   Using setOn(!on) works but can cause stale state; initial boolean is valid; wrapping button is not required.

3. Final Answer:

   The event handler attribute should be 'onClick' with capital C. -> Option C

4. Quick Check:

   Event handlers use camelCase 'onClick' [OK]

Hint: React event handlers always use camelCase like 'onClick' [OK]

Common Mistakes:

• Using lowercase 'onclick' instead of 'onClick'
• Ignoring stale state issues in setState
• Thinking JSX requires fragments for single elements

5. You want to create a Next.js client component with a text input that updates a greeting message live as the user types. Which approach correctly uses event handlers and state to achieve this?

import { useState } from 'react';

export default function Greeting() {
  const [name, setName] = useState('');

  // What should the input's onChange handler be?
  return (
    

      
      
Hello, {name || 'stranger'}!
    
  );
}

hard

A. onChange={e => setName(e.target.value)}

B. onChange={setName(e.target.value)}

C. onChange={() => setName('')}

D. onChange={e => e.target.value}

Solution

1. Step 1: Understand event handler for input changes

   The onChange handler receives an event; to update state, call setName with event target's value.

2. Step 2: Identify correct arrow function syntax

   onChange={e => setName(e.target.value)} correctly defines an arrow function that takes event and calls setName with e.target.value.

3. Final Answer:

   onChange={e => setName(e.target.value)} -> Option A

4. Quick Check:

   Use event parameter to update state from input value [OK]

Hint: Use arrow function with event to update state from input [OK]

Common Mistakes:

• Calling setName immediately instead of in a function
• Not passing event parameter to handler
• Returning value without updating state