Event handlers in client components in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of event handlers in client components?

Event handlers let components respond to user actions like clicks or typing, making the app interactive.

beginner

How do you attach a click event handler to a button in a Next.js client component?

Use the onClick attribute with a function, for example: <button onClick={() => alert('Clicked!')}>Click me</button>.

intermediate

Why must client components use the use client directive when handling events?

Because event handlers need to run in the browser, the use client directive tells Next.js to make the component run on the client side.

intermediate

What is the difference between passing a function directly and calling it inside an event handler?

Passing a function like onClick={handleClick} means it runs on click. Calling it like onClick={handleClick()} runs it immediately, which is usually wrong.

intermediate

How can you prevent the default browser behavior in an event handler?

Inside the event handler, call event.preventDefault() to stop the browser's default action, like following a link or submitting a form.

Which directive must you add at the top of a Next.js component to use event handlers?

A "use event"

B "use client"

C "use strict"

D "use server"

The "use client" directive tells Next.js to run the component on the client side, enabling event handlers.

How do you correctly attach a click handler that calls a function named handleClick?

A <code>onClick="handleClick()"</code>

B <code>onClick={handleClick()}</code>

C <code>onClick={handleClick}</code>

D <code>onClick={() =&gt; handleClick}</code>

You pass the function reference without calling it: onClick={handleClick}.

What does event.preventDefault() do inside an event handler?

A Triggers the event again

B Stops the event from bubbling up

C Logs the event to the console

D Stops the browser's default action

It prevents the browser from doing its default behavior, like following a link or submitting a form.

Where do event handlers run in Next.js client components?

A In the browser (client side)

B On the server

C In the database

D In the build process

Event handlers run in the browser to respond to user actions.

Which of these is a valid way to define an event handler function inside a Next.js client component?

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

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

C handleClick = () => alert('Clicked!')

D def handleClick(): alert('Clicked!')

The arrow function syntax with const is valid in React/Next.js components.

Explain how to add a click event handler to a button in a Next.js client component and why the "use client" directive is necessary.

Think about where the code runs and how React handles events.

Describe how to prevent a form submission from refreshing the page using an event handler in a Next.js client component.

Focus on stopping default browser behavior.

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