State and hooks in client components in NextJS

Introduction

State lets your component remember things like user input or clicks. Hooks are special tools that help you add state and other features easily.

When you want to remember what a user types in a form.

When you want to show or hide parts of the page after a button click.

When you want to update the page without reloading it.

When you want to keep track of a counter or timer.

When you want to fetch data and show loading or error messages.

Syntax

NextJS

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

export default function MyComponent() {
  const [state, setState] = useState(null);

  return (
    <div>
      {/* UI using state */}
    </div>
  );
}

Always add 'use client'; at the top of your file to make it a client component in Next.js.

useState returns an array with the current value and a function to update it.

Examples

This example shows a simple counter that increases when you click the button.

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>
  );
}

This example toggles text between ON and OFF when clicked.

NextJS

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

export default function Toggle() {
  const [isOn, setIsOn] = useState(false);

  return (
    <button onClick={() => setIsOn(!isOn)}>
      {isOn ? 'ON' : 'OFF'}
    </button>
  );
}

Sample Program

This component lets the user type their name. It remembers what they type and shows a greeting that updates as they type.

It uses useState to keep track of the input value and updates the greeting live.

NextJS

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

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

  return (
    <main style={{ padding: '1rem', fontFamily: 'Arial, sans-serif' }}>
      <label htmlFor="nameInput">Enter your name:</label><br />
      <input
        id="nameInput"
        type="text"
        value={name}
        onChange={e => setName(e.target.value)}
        aria-label="Name input"
        style={{ marginTop: '0.5rem', padding: '0.5rem', fontSize: '1rem' }}
      />
      <p style={{ marginTop: '1rem', fontSize: '1.2rem' }}>
        Hello, {name || 'stranger'}!
      </p>
    </main>
  );
}

Important Notes

Client components run in the browser and can use hooks like useState.

Always start client components with 'use client'; in Next.js 14+.

Updating state causes the component to re-render and show the latest data.

Summary

State lets components remember and update data over time.

Hooks like useState make adding state easy and clean.

Client components in Next.js need 'use client'; to use hooks and state.

Practice

1. What is the main purpose of using useState in a Next.js client component?

easy

A. To fetch data from the server before rendering

B. To store and update data that changes over time within the component

C. To style the component dynamically

D. To navigate between pages automatically

Solution

1. Step 1: Understand what useState does

   useState is a React hook that allows components to keep track of data that can change, like user input or toggles.

2. Step 2: Identify the purpose in Next.js client components

   In Next.js client components, useState helps remember and update values without reloading the page.

3. Final Answer:

   To store and update data that changes over time within the component -> Option B

4. Quick Check:

   State = Remember and update data [OK]

Hint: Remember: useState stores changing data inside components [OK]

Common Mistakes:

• Thinking useState fetches server data
• Confusing useState with styling or navigation
• Forgetting useState only works in client components

2. Which of the following is the correct way to declare a state variable called count with initial value 0 in a Next.js client component?

easy

A. const [count, setCount] = useState(0);

B. const count = useState(0);

C. let count = useState(0);

D. const count = useState()[0];

Solution

1. Step 1: Recall the syntax of useState hook

   The correct syntax uses array destructuring: const [state, setState] = useState(initialValue);

2. Step 2: Match the syntax with the variable name and initial value

   For count starting at 0, it should be const [count, setCount] = useState(0);

3. Final Answer:

   const [count, setCount] = useState(0); -> Option A

4. Quick Check:

   useState syntax = [state, setState] [OK]

Hint: Use array destructuring: [value, setValue] = useState() [OK]

Common Mistakes:

• Assigning useState directly to a single variable
• Using let instead of const for state
• Not using array destructuring syntax

3. Consider this Next.js client component code:

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

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

What will be displayed after clicking the button three times?

medium

A. Count: 0

B. Count: 1

C. Count: 3

D. Count: undefined

Solution

1. Step 1: Understand initial state and button click effect

   The initial count is 0. Each click calls setCount(count + 1), increasing count by 1.

2. Step 2: Calculate count after three clicks

   After 1 click: count = 1
   After 2 clicks: count = 2
   After 3 clicks: count = 3

3. Final Answer:

   Count: 3 -> Option C

4. Quick Check:

   Increment count 3 times = 3 [OK]

Hint: Each click adds 1 to count state [OK]

Common Mistakes:

• Thinking count resets on each render
• Confusing initial value with updated value
• Ignoring that setCount updates state asynchronously

4. What is wrong with this Next.js client component code?

import { useState } from 'react';

export default function Toggle() {
  const [isOn, setIsOn] = useState(false);
  return (
     setIsOn(!isOn)}>
      {isOn ? 'ON' : 'OFF'}
    
  );
}

medium

A. State variable should be declared with let

B. Incorrect use of useState syntax

C. Button onClick handler is invalid

D. Missing 'use client'; directive at the top

Solution

1. Step 1: Check for client component requirement

   Hooks like useState require the component to be a client component, which needs 'use client'; at the top.

2. Step 2: Verify code for missing directive

   The code lacks 'use client'; at the top, so it will cause an error in Next.js.

3. Final Answer:

   Missing 'use client'; directive at the top -> Option D

4. Quick Check:

   Client components need 'use client' [OK]

Hint: Always add 'use client'; on top when using hooks [OK]

Common Mistakes:

• Forgetting 'use client' directive
• Thinking useState syntax is wrong
• Assuming onClick handler is invalid

5. You want to create a Next.js client component that toggles between showing and hiding a message when a button is clicked. Which code snippet correctly implements this behavior?

hard

A. "use client";
import { useState } from 'react';

export default function ShowHide() {
const [visible, setVisible] = useState(false);
return (
<>
setVisible(!visible)}>
{visible ? 'Hide' : 'Show'} Message

{visible && Hello, this is the message!}
</>
);
}

B. "use client";
import { useState } from 'react';

export default function ShowHide() {
const visible = false;
return (
<>
(visible = !visible)}>
{visible ? 'Hide' : 'Show'} Message

{visible && Hello, this is the message!}
</>
);
}

C. import { useState } from 'react';

export default function ShowHide() {
const [visible, setVisible] = useState(false);
return (
<>
setVisible(!visible)}>
{visible ? 'Hide' : 'Show'} Message

{visible && Hello, this is the message!}
</>
);
}

D. "use client";
import { useState } from 'react';

export default function ShowHide() {
const [visible, setVisible] = useState(false);
return (
<>
setVisible(visible)}>
{visible ? 'Hide' : 'Show'} Message

{visible && Hello, this is the message!}
</>
);
}

Solution

1. Step 1: Check for 'use client' directive and useState usage

   "use client"; import { useState } from 'react'; export default function ShowHide() { const [visible, setVisible] = useState(false); return ( <> setVisible(!visible)}> {visible ? 'Hide' : 'Show'} Message {visible &&

   Hello, this is the message!

   } </> ); } correctly includes 'use client'; and uses useState to track visibility state.

2. Step 2: Verify toggle logic and rendering

   The button toggles visible state with setVisible(!visible), and the message shows only when visible is true.

3. Final Answer:

   Option A code snippet correctly implements the toggle behavior -> Option A

4. Quick Check:

   Toggle state with useState and 'use client' [OK]

Hint: Use useState and 'use client'; toggle with setVisible(!visible) [OK]

Common Mistakes:

• Not adding 'use client' directive
• Trying to change state variable directly
• Passing current state to setter without toggling