Dynamic rendering triggers in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is dynamic rendering in Next.js?

Dynamic rendering in Next.js means the page content is generated on the server or client when requested, allowing fresh data or personalized content each time.

beginner

Name two common triggers that cause dynamic rendering in Next.js.

Triggers include URL parameters changing (like dynamic routes) and user interactions that fetch new data (like client-side navigation or API calls).

intermediate

How does Next.js decide when to re-render a page dynamically with Incremental Static Regeneration (ISR)?

Next.js re-renders a page dynamically when the set revalidation time expires, allowing the page to update with fresh data without rebuilding the whole site.

intermediate

What role do server actions play in dynamic rendering triggers in Next.js 14+?

Server actions let you run server code on user events, triggering dynamic rendering by updating data or state without full page reloads.

beginner

Why is dynamic rendering important for user experience in Next.js apps?

It ensures users see up-to-date, personalized content quickly, improving engagement and making apps feel responsive and alive.

Which event can trigger dynamic rendering in Next.js?

A Changing URL parameters

B Static HTML file creation

C Using CSS styles

D Adding comments in code

Changing URL parameters triggers Next.js to render new content dynamically for that route.

What does ISR stand for in Next.js dynamic rendering?

A Instant Server Response

B Internal State Refresh

C Incremental Static Regeneration

D Interactive Static Routing

ISR means Incremental Static Regeneration, allowing pages to update after a set time.

Which Next.js feature lets you run server code on user actions to trigger dynamic rendering?

A Client-side CSS

B Static Props

C Image Optimization

D Server Actions

Server Actions run server code on user events, triggering dynamic updates.

Dynamic rendering helps improve user experience by:

A Making pages load slower

B Showing fresh and personalized content

C Removing all images

D Disabling navigation

Dynamic rendering ensures users see updated and personalized content quickly.

Which of these is NOT a trigger for dynamic rendering in Next.js?

A Editing CSS files without rebuilding

B Changing the page URL

C Revalidation time expires in ISR

D User clicks a button that fetches new data

Editing CSS files alone does not trigger dynamic rendering; it requires rebuilding or hot reload.

Explain how dynamic rendering triggers work in Next.js and why they matter.

Think about when and why Next.js updates page content dynamically.

Describe how Incremental Static Regeneration (ISR) controls dynamic rendering in Next.js.

Focus on how ISR balances static and dynamic content.

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