Use server directive in NextJS - Step-by-Step Execution

Concept Flow - Use server directive

Start Component File

↓

Add 'use server' Directive

↓

Define Server-only Functions

↓

Export Component

↓

Next.js Server Processes Component

↓

Server-only Code Runs on Server

↓

Client Receives Rendered Output

↓

Client Interacts with Component

↓

Server Functions Can Be Called via Server Actions

The 'use server' directive marks functions to run only on the server, separating server logic from client code in Next.js components.

Execution Sample

NextJS

"use server";

async function saveData(formData) {
  const data = formData.get("data");
  // server-only logic
}

export default function Page() {
  return (
    <form action={saveData}>
      <input type="hidden" name="data" value="info" />
      <button type="submit">Save</button>
    </form>
  );
}

This code marks saveData as server-only, so it runs on the server when the form is submitted via the button.

Execution Table

Step	Action	Code Evaluated	Result	Notes
1	Read file	"use server" directive found	Mark functions below as server-only	Server-only functions separated
2	Define saveData	async function saveData(formData)	Function saved as server-only	Not bundled to client
3	Export Page component	function Page()	Component ready for rendering	Client and server parts separated
4	Render Page on server	JSX <button>	Button HTML generated	Sent to client
5	Client loads page	Button rendered	User sees button	Client can interact
6	User clicks button	form submission triggers saveData(formData)	Server action called	Runs saveData on server
7	saveData runs	saveData(formData)	Data saved on server	No client code runs saveData
8	Return response	saveData completes	Client updates if needed	Server-client interaction done
9	Exit	No more actions	Process complete	Server directive enforced

💡 Execution stops after server function completes and client updates if needed

Variable Tracker

Variable	Start	After Step 2	After Step 6	Final
saveData	undefined	Function defined (server-only)	Function called with formData	Function completes execution
Page	undefined	Function defined	Rendered on client	Component remains unchanged

Key Moments - 2 Insights

Why does the saveData function not run on the client?

Because of the 'use server' directive (see execution_table step 1), Next.js treats saveData as server-only and excludes it from client bundles.

How does the client trigger the server-only saveData function?

The client triggers it via a server action call on button click (execution_table step 6), which runs the function on the server.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what happens?

A The server renders the button HTML to send to the client

B The client runs the saveData function

C The saveData function is defined on the client

D The button is clicked by the user

💡 Hint

Check step 4 in execution_table where rendering happens on the server

At which step does the saveData function run on the server?

A Step 6

B Step 7

C Step 3

D Step 5

💡 Hint

Look at step 7 in execution_table where saveData executes

If the 'use server' directive was removed, what would change in the execution?

A The button would not render

B The saveData function would still run on the server

C saveData would run on the client instead of the server

D The component would fail to compile

💡 Hint

Refer to variable_tracker and key_moments about server-only function behavior

Concept Snapshot

"use server" directive in Next.js
- Place at top of file to mark server-only functions
- Server-only functions run only on server, not bundled to client
- Client calls server functions via server actions
- Helps separate server logic from client UI
- Improves security and performance by isolating server code

Full Transcript

The 'use server' directive in Next.js marks functions to run only on the server. When Next.js reads a component file with this directive, it separates server-only functions from client code. The server renders the component's HTML and sends it to the client. When the user interacts, such as clicking a button, the client triggers server actions that call the server-only functions. This keeps server logic secure and prevents it from running on the client. The execution table shows each step from reading the directive, defining functions, rendering, client interaction, to server function execution and completion.