Interleaving server and client in NextJS

Introduction

Interleaving server and client means mixing server-side and client-side code in one component. This helps you load data on the server and add interactive parts on the client smoothly.

You want to fetch data on the server for faster loading but add buttons that users can click on the client.

You need to show a list from the server but allow users to filter it without reloading the page.

You want to keep SEO benefits by rendering content on the server but still have client-side animations or effects.

You want to use React Server Components for data fetching and React Client Components for user interaction in the same page.

Syntax

NextJS

import React from 'react';
import ClientComponent from './ClientComponent';

// Server Component
export default async function Page() {
  const data = await fetch('https://api.example.com/data').then(res => res.json());

  return (
    <main>
      <h1>Server Data</h1>
      <ClientComponent items={data.items} />
    </main>
  );
}

// Client Component
'use client';
import { useState } from 'react';

export default function ClientComponent({ items }) {
  const [count, setCount] = useState(0);

  return (
    <section>
      <p>Items count: {items.length}</p>
      <button onClick={() => setCount(count + 1)}>Clicked {count} times</button>
    </section>
  );
}

Server Components run only on the server and can fetch data directly.

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

Examples

This is a client-only component that uses state and runs in the browser.

NextJS

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

export default function ClientOnly() {
  const [text, setText] = useState('');
  return <input value={text} onChange={e => setText(e.target.value)} />;
}

This is a server-only component that fetches data before rendering.

NextJS

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

This shows how to use a client component inside a server component.

NextJS

import ClientComponent from './ClientComponent';

export default async function Page() {
  const data = await fetch('https://api.example.com/data').then(r => r.json());
  return <ClientComponent items={data.items} />;
}

Sample Program

This example shows a server component fetching a list of fruits and passing it to a client component. The client component displays the count and has a button that updates a click counter interactively.

This way, data loads fast from the server, and the button works smoothly on the client.

NextJS

import React from 'react';
import ClientComponent from './ClientComponent';

// Server Component
export default async function Page() {
  // Simulate fetching data on server
  const data = { items: ['apple', 'banana', 'cherry'] };

  return (
    <main>
      <h1>Fruits List</h1>
      <ClientComponent items={data.items} />
    </main>
  );
}

// Client Component
'use client';
import { useState } from 'react';

export default function ClientComponent({ items }) {
  const [count, setCount] = useState(0);

  return (
    <section>
      <p>We have {items.length} fruits.</p>
      <button onClick={() => setCount(count + 1)} aria-label="Click counter">
        Clicked {count} times
      </button>
    </section>
  );
}

Important Notes

Always mark client components with 'use client'; at the top.

Server components can fetch data directly without extra hooks.

Client components can use React hooks like useState for interactivity.

Summary

Interleaving lets you mix server data fetching with client interactivity.

Use server components for loading data and client components for user actions.

This approach improves performance and user experience in Next.js apps.

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