Dynamic rendering triggers in NextJS - Step-by-Step Execution

Concept Flow - Dynamic rendering triggers

User Request

↓

Check Rendering Mode

↓

Static

↓

Serve Cached

↓

Fetch Data / Compute

↓

Render Updated Page

↓

Send Response to User

When a user requests a page, Next.js decides if it serves a cached static page or runs server code to dynamically render fresh content.

Execution Sample

NextJS

export default function Page() {
  const time = new Date().toLocaleTimeString();
  return <p>Current time: {time}</p>;
}

This component dynamically renders the current time on each request.

Execution Table

Step	Trigger	Server Code Run?	Data Fetched	Rendered Output	Response Sent
1	User requests page	Yes	Current time fetched	Rendered with current time	Page sent with fresh time
2	User refreshes page	Yes	New current time fetched	Rendered with new time	Page sent with updated time
3	No further requests	No	No data fetched	No rendering	No response

💡 Execution stops when no user requests occur.

Variable Tracker

Variable	Start	After 1	After 2	Final
time	undefined	e.g. 10:15:30 AM	e.g. 10:15:45 AM	latest fetched time

Key Moments - 2 Insights

Why does the server code run on every request in dynamic rendering?

Because dynamic rendering means Next.js runs the server code each time to fetch fresh data, as shown in execution_table steps 1 and 2.

What happens if no user requests come in?

No server code runs and no page is rendered or sent, as shown in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution table, what happens at step 2?

A Page served from cache without running server code

B Server code runs and page renders with new time

C No response sent to user

D Server code runs but no data fetched

💡 Hint

Check the 'Server Code Run?' and 'Rendered Output' columns at step 2.

At which step does the server NOT run code?

A Step 3

B Step 2

C Step 1

D None, server always runs code

💡 Hint

Look at the 'Server Code Run?' column for each step.

If the page was static, how would the execution table change?

A Server code runs on every request

B No response sent to user

C Page served from cache without server code running

D Data fetched on every request

💡 Hint

Static pages serve cached content without running server code each time.

Concept Snapshot

Dynamic rendering in Next.js means server code runs on each user request.
This fetches fresh data and renders the page anew.
If no requests come, no rendering happens.
Static pages serve cached content without server code running.
Dynamic rendering ensures up-to-date content every time.

Full Transcript

Dynamic rendering triggers in Next.js happen when a user requests a page. The server checks if the page should be rendered dynamically or served statically. For dynamic pages, server code runs on every request to fetch fresh data and render the page. This is shown in the execution table where each user request triggers server code execution, data fetching, and rendering. If no requests occur, no server code runs and no page is sent. This ensures users always see the latest content. Static pages skip server code on requests and serve cached content instead.

Practice

1. Which React hook in Next.js is primarily used to trigger a component re-render when data changes dynamically?

easy

A. useRef

B. useEffect

C. useState

D. useContext

Solution

1. Step 1: Understand the purpose of useState

   useState creates a state variable that, when updated, triggers a re-render of the component.

2. Step 2: Compare with other hooks

   useEffect runs side effects but does not itself trigger re-renders; useRef holds mutable values without causing re-renders; useContext shares data but depends on context changes.

3. Final Answer:

   useState -> Option C

4. Quick Check:

   State change triggers re-render = useState [OK]

Hint: State updates cause re-render; useState manages state [OK]

Common Mistakes:

• Confusing useEffect as a trigger for re-render
• Using useRef expecting re-render on change
• Thinking useContext alone triggers re-render

2. Which of the following is the correct syntax to update state in a Next.js functional component using useState?

easy

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

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

C. const count = useState(0); count = 5;

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

Solution

1. Step 1: Review correct useState syntax

   useState returns an array with current state and a setter function. The setter function is called with the new value to update state.

2. Step 2: Identify correct setter usage

   Only setCount(5); correctly calls the setter function. Assigning directly to setCount or count is invalid.

3. Final Answer:

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

4. Quick Check:

   Call setter function with new value = setCount(5) [OK]

Hint: Call setter function like setCount(newValue) [OK]

Common Mistakes:

• Assigning value directly to setter function
• Trying to call state variable as a function
• Ignoring array destructuring from useState

3. Given the following Next.js component, what will be displayed after clicking the button twice?

import { useState } from 'react';

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

medium

A. Count: 2

B. Count: 1

C. Count: 0

D. Count: NaN

Solution

1. Step 1: Understand initial state and button action

   Initial count is 0. Each button click calls setCount(count + 1), increasing count by 1.

2. Step 2: Calculate count after two clicks

   After first click: count = 1; after second click: count = 2.

3. Final Answer:

   Count: 2 -> Option A

4. Quick Check:

   Increment twice from 0 = 2 [OK]

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

Common Mistakes:

• Assuming state does not update immediately
• Confusing initial value with updated value
• Expecting NaN due to wrong state usage

4. Identify the error in this Next.js component that tries to update state on button click:

import { useState } from 'react';

export default function Example() {
  const [value, setValue] = useState('');

  function handleClick() {
    value = 'Updated';
  }

  return (
    <>
      
{value}
      Update
    </>
  );
}

medium

A. Missing import of React

B. useState initial value must be a number

C. Button onClick should be a string

D. Directly assigning to state variable instead of using setter

Solution

1. Step 1: Check how state is updated

   The function handleClick assigns directly to value, which is a state variable and read-only.

2. Step 2: Correct way to update state

   State must be updated by calling the setter function setValue('Updated') to trigger re-render.

3. Final Answer:

   Directly assigning to state variable instead of using setter -> Option D

4. Quick Check:

   Use setter function to update state [OK]

Hint: Never assign state variable directly; use setter function [OK]

Common Mistakes:

• Assigning state variable directly
• Forgetting to call setter function
• Confusing state variable with setter

5. You want a Next.js component to fetch user data dynamically when the component mounts and update the UI accordingly. Which approach correctly triggers dynamic rendering and cleans up properly?

import { useState, useEffect } from 'react';

export default function UserProfile() {
  const [user, setUser] = useState(null);

  useEffect(() => {
    let isMounted = true;
    fetch('/api/user')
      .then(res => res.json())
      .then(data => {
        if (isMounted) setUser(data);
      });
    return () => { isMounted = false; };
  }, []);

  if (!user) return <p>Loading...</p>;
  return <p>Hello, {user.name}!</p>;
}

hard

A. Correct: fetch in useEffect with cleanup flag to avoid setting state after unmount

B. Incorrect: fetch outside useEffect causes infinite re-renders

C. Incorrect: setting state directly without useEffect causes errors

D. Incorrect: missing dependency array causes fetch to run once

Solution

1. Step 1: Analyze data fetching inside useEffect

   Fetching data inside useEffect with empty dependency array runs once on mount, triggering dynamic rendering when data arrives.

2. Step 2: Understand cleanup with isMounted flag

   The isMounted flag prevents setting state if the component unmounts before fetch completes, avoiding memory leaks or errors.

3. Final Answer:

   Correct: fetch in useEffect with cleanup flag to avoid setting state after unmount -> Option A

4. Quick Check:

   Fetch in useEffect + cleanup = safe dynamic update [OK]

Hint: Use useEffect with cleanup to fetch and update safely [OK]

Common Mistakes:

• Fetching data outside useEffect causing repeated renders
• Not cleaning up async calls causing memory leaks
• Missing dependency array causing multiple fetches