Interleaving server and client in NextJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What will this Next.js component render?

Consider this Next.js 14 component using server and client code interleaving. What will be the rendered output in the browser?

NextJS

import { cookies } from 'next/headers';

export default function Greeting() {
  const cookieStore = cookies();
  const user = cookieStore.get('user')?.value ?? 'Guest';

  return (
    <main>
      <h1>Hello, {user}!</h1>
      <ClientButton />
    </main>
  );
}

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

function ClientButton() {
  const [count, setCount] = useState(0);
  return (
    <button onClick={() => setCount(count + 1)} aria-label="Increment count">
      Clicked {count} times
    </button>
  );
}

A <main><h1>Hello, Guest!</h1><button>Clicked 0 times</button></main>

B <main><h1>Hello, undefined!</h1><button>Clicked 0 times</button></main>

C <main><h1>Hello, !</h1><button>Clicked 0 times</button></main>

D <main><h1>Hello, user!</h1><button>Clicked 0 times</button></main>

💡 Hint

Remember that cookies() runs on the server and returns cookie values if present, otherwise fallback is used.

The server component reads cookies on the server side. If no 'user' cookie is set, it defaults to 'Guest'. The client component renders a button with initial count 0.

❓ state_output

intermediate

What is the button label after clicking twice?

Given this Next.js client component inside a server component, what will the button label show after clicking it twice?

NextJS

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

export default function Counter() {
  const [count, setCount] = useState(0);
  return (
    <button onClick={() => setCount(count + 1)} aria-label="Increment">
      Clicked {count} times
    </button>
  );
}

A Clicked 1 times

B Clicked 2 times

C Clicked 0 times

D Clicked NaN times

💡 Hint

Each click increments the count state by 1.

The useState hook starts count at 0. Each click adds 1, so after two clicks, count is 2.

📝 Syntax

advanced

Which option correctly imports and uses a client component inside a server component?

In Next.js 14, you want to use a client component named inside a server component. Which code snippet is correct?

A

import ClientWidget from './ClientWidget';

export default function ServerComp() {
  'use client';
  return <ClientWidget />;
}

B

'use client';
import ClientWidget from './ClientWidget';

export default function ServerComp() {
  return <ClientWidget />;
}

C

import ClientWidget from './ClientWidget';

export default function ServerComp() {
  return <ClientWidget />;
}

// ClientWidget has 'use client' directive

D

import ClientWidget from './ClientWidget';

export default function ServerComp() {
  return <ClientWidget />;
}

// ServerComp has 'use client' directive

💡 Hint

Server components do not have 'use client' directive. Client components must have it.

Server components can import client components without 'use client' directive themselves. The client component file must have 'use client'.

🔧 Debug

advanced

Why does this Next.js component cause a hydration error?

This Next.js component mixes server and client code. Why does it cause a hydration mismatch error in the browser? Code: import { cookies } from 'next/headers'; export default function Page() { const user = cookies().get('user')?.value ?? 'Guest'; return (

Welcome, {user}

); }

A The component is missing a React key prop on the button, causing hydration error.

B The cookies() call is invalid in server components, causing runtime error.

C The button element is missing an aria-label, causing hydration error.

D Using cookies() in a server component is fine, but the button with onClick requires 'use client' directive, causing mismatch.

💡 Hint

Client interactivity requires 'use client' directive on the component or a child component.

Server components cannot have event handlers like onClick directly. The button with onClick must be in a client component with 'use client' directive to avoid hydration mismatch.

🧠 Conceptual

expert

What is the main benefit of interleaving server and client components in Next.js 14?

Next.js 14 allows mixing server and client components in the same UI tree. What is the primary advantage of this approach?

A It enables faster page loads by rendering static parts on the server and interactive parts on the client efficiently.

B It forces all components to run on the client, improving interactivity at the cost of performance.

C It requires all components to be server components, simplifying deployment but reducing interactivity.

D It disables server-side rendering, making the app fully client-rendered for easier debugging.

💡 Hint

Think about balancing performance and interactivity in modern web apps.

Interleaving lets Next.js render static or data-heavy parts on the server for speed, while client components handle user interaction, giving best of both worlds.

Practice

1. In Next.js, what is the main benefit of interleaving server and client components?

easy

A. It disables server-side rendering completely.

B. It improves performance by loading data on the server and handling interactions on the client.

C. It forces all components to run only on the client side.

D. It allows you to write all code in one file without separation.

Solution

1. Step 1: Understand server and client roles

   Server components fetch data and render HTML, while client components handle user interactions.

2. Step 2: Identify the benefit of mixing them

   Combining them improves performance by reducing client work and speeding up data loading.

3. Final Answer:

   It improves performance by loading data on the server and handling interactions on the client. -> Option B

4. Quick Check:

   Interleaving = Better performance [OK]

Hint: Remember: server for data, client for interaction [OK]

Common Mistakes:

• Thinking all code runs only on client
• Believing interleaving disables server rendering
• Assuming no performance benefit

2. Which of the following is the correct way to mark a React component as a client component in Next.js?

easy

A. Add client: true in the component's props.

B. Wrap the component with <ClientComponent> tags.

C. Use export default clientComponent() instead of a normal export.

D. Add the directive 'use client' at the top of the file.

Solution

1. Step 1: Recall client component syntax

   Next.js requires 'use client' directive at the top of the file to mark it as client.

2. Step 2: Check other options

   Wrapping tags, special exports, or props flags are not valid Next.js patterns.

3. Final Answer:

   Add the directive 'use client' at the top of the file. -> Option D

4. Quick Check:

   Client component directive = 'use client' [OK]

Hint: Look for 'use client' at file top to mark client components [OK]

Common Mistakes:

• Trying to wrap components with special tags
• Using props to mark client components
• Confusing export syntax for client marking

3. Given this Next.js code snippet, what will be rendered on the page?

export default function ServerComponent() {
  const data = fetch('https://api.example.com/data').then(res => res.json());
  return (
    <div>
      <ClientComponent />
      <p>Data loaded</p>
    </div>
  );
}

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

medium

A. Only the paragraph 'Data loaded' because ClientComponent is not marked as client.

B. A button showing 'Clicked 0 times' and a paragraph 'Data loaded'.

C. An error because fetch is used incorrectly in ServerComponent.

D. Nothing renders because ClientComponent is inside ServerComponent.

Solution

1. Step 1: Check ClientComponent usage

   ClientComponent uses useState, so it must be marked with 'use client' directive to work as client component.

2. Step 2: Analyze missing 'use client' directive

   Without 'use client', ClientComponent is treated as server component, but hooks are invalid there, causing it not to render properly.

3. Final Answer:

   Only the paragraph 'Data loaded' because ClientComponent is not marked as client. -> Option A

4. Quick Check:

   Missing 'use client' = ClientComponent won't render [OK]

Hint: Client components need 'use client' directive to render hooks [OK]

Common Mistakes:

• Assuming ClientComponent renders without 'use client'
• Thinking fetch usage causes error here
• Believing nested client components always render

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

'use client';

export default function ClientComponent() {
  const data = fetch('https://api.example.com/data').then(res => res.json());
  return <div>Data count: {data.length}</div>;
}

medium

A. Missing 'use server' directive at the top of the file.

B. The component should not return JSX inside a client component.

C. Using fetch directly in a client component without async/await causes a Promise error.

D. The fetch URL is invalid syntax.

Solution

1. Step 1: Understand fetch in client components

   fetch returns a Promise; using it directly without awaiting causes data to be a Promise, not the actual data.

2. Step 2: Identify the error in rendering

   Trying to access data.length on a Promise causes runtime error because Promise has no length property.

3. Final Answer:

   Using fetch directly in a client component without async/await causes a Promise error. -> Option C

4. Quick Check:

   Fetch returns Promise; must await in client [OK]

Hint: Always await fetch in client components to get data [OK]

Common Mistakes:

• Thinking 'use server' is needed in client components
• Believing JSX can't be returned in client components
• Assuming fetch URL syntax is wrong

5. You want to display a list of products fetched on the server and allow users to add products to a cart on the client. Which is the best way to interleave server and client components in Next.js?

hard

A. Fetch products in a server component and render a client component for the add-to-cart buttons inside it.

B. Fetch products inside a client component and handle add-to-cart in the same component.

C. Fetch products in a client component and render server components for buttons.

D. Fetch products and handle add-to-cart both in server components only.

Solution

1. Step 1: Separate data fetching and interactivity

   Fetching products is best done on the server for performance and SEO benefits.

2. Step 2: Use client components for user actions

   Add-to-cart buttons require client interactivity, so they should be client components nested inside the server component.

3. Final Answer:

   Fetch products in a server component and render a client component for the add-to-cart buttons inside it. -> Option A

4. Quick Check:

   Server fetch + client interactivity = Fetch products in a server component and render a client component for the add-to-cart buttons inside it. [OK]

Hint: Server fetch data, client handle clicks inside [OK]

Common Mistakes:

• Fetching data on client causing slower load
• Trying to handle interactivity in server components
• Rendering server components inside client components incorrectly