Revalidation after mutation in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does revalidatePath do in Next.js after a mutation?

revalidatePath tells Next.js to refresh the cached data for a specific path. This updates the page with fresh data after a change (mutation) happens.

beginner

Why is revalidation important after a mutation in Next.js?

Because after changing data (mutation), the page might show old info. Revalidation updates the page so users see the latest data without needing a full reload.

beginner

Which Next.js function can you use to revalidate a specific page path after data changes?

You use revalidatePath('/your-path') to refresh the cached data for that page.

intermediate

How does revalidatePath improve user experience in Next.js apps?

It keeps the page data fresh after updates without full reloads, making the app feel faster and more responsive.

beginner

What is a common scenario where you should call revalidatePath in Next.js?

After a user submits a form that changes data, like adding a comment or updating a profile, call revalidatePath to update the page content.

What is the main purpose of revalidatePath in Next.js?

A To refresh cached page data after a mutation

B To reload the entire browser window

C To delete user cookies

D To change the URL path

revalidatePath refreshes cached data for a page after data changes, ensuring fresh content.

When should you call revalidatePath in a Next.js app?

A When changing CSS styles

B Before the app loads

C Only on initial page load

D After a data mutation like form submission

It is called after data changes to update the page content.

Which of these is NOT a benefit of revalidation after mutation?

A Automatically fixing code bugs

B Improving app responsiveness

C Showing fresh data without full reload

D Keeping user view up to date

Revalidation updates data but does not fix code bugs automatically.

What argument does revalidatePath require?

A The user's ID

B The entire page HTML

C The URL path string to revalidate

D The CSS file path

You provide the path string of the page you want to refresh.

Which Next.js feature does revalidatePath relate to?

A Image optimization

B Incremental Static Regeneration (ISR)

C Client-side routing

D API routes

It is part of ISR to update static pages after data changes.

Explain how you would keep a Next.js page updated after a user changes data on the site.

Think about refreshing cached data after a change.

Describe the role of revalidation in Next.js Incremental Static Regeneration.

Focus on how static pages get updated after data changes.

Practice

1. What is the main purpose of revalidation after mutation in Next.js App Router?

easy

A. To update the page data after a change so the UI shows fresh information

B. To prevent any data changes from being saved

C. To reload the entire website from scratch

D. To disable user interactions temporarily

Solution

1. Step 1: Understand mutation effect

   When data changes (mutation), the UI might show old data if not updated.

2. Step 2: Purpose of revalidation

   Revalidation reloads or refreshes data so the UI reflects the latest changes.

3. Final Answer:

   To update the page data after a change so the UI shows fresh information -> Option A

4. Quick Check:

   Revalidation updates data = A [OK]

Hint: Revalidation means refreshing data after changes [OK]

Common Mistakes:

• Thinking revalidation stops data saving
• Confusing revalidation with full page reload
• Believing it disables user actions

2. Which Next.js App Router method is used to trigger revalidation after a mutation?

easy

A. router.replace()

B. router.reload()

C. router.push()

D. router.refresh()

Solution

1. Step 1: Identify method for revalidation

   Next.js App Router provides router.refresh() to reload data without full page reload.

2. Step 2: Differentiate from other methods

   router.reload() reloads whole page, router.push() and router.replace() change routes.

3. Final Answer:

   router.refresh() -> Option D

4. Quick Check:

   Revalidation uses router.refresh() = A [OK]

Hint: Use router.refresh() to reload data after mutation [OK]

Common Mistakes:

• Using router.reload() which reloads full page
• Confusing route navigation methods with revalidation
• Trying to use router.replace() for data refresh

3. Given this code snippet in a Next.js component:

import { useRouter } from 'next/navigation';

export default function UpdateButton() {
  const router = useRouter();

  async function handleClick() {
    await fetch('/api/update', { method: 'POST' });
    router.refresh();
  }

  return Update;
}

What happens when the button is clicked?

medium

A. The API is called, then the page data refreshes without full reload

B. Nothing happens because router.refresh() is incorrect

C. The page reloads completely, losing state

D. The button click causes a navigation to /api/update

Solution

1. Step 1: Analyze handleClick function

   It calls the API with POST, then calls router.refresh() to reload data.

2. Step 2: Understand router.refresh() effect

   This refreshes the current route's data without a full page reload or navigation.

3. Final Answer:

   The API is called, then the page data refreshes without full reload -> Option A

4. Quick Check:

   API call + router.refresh() updates data = C [OK]

Hint: router.refresh() updates data without full reload [OK]

Common Mistakes:

• Thinking router.refresh() reloads entire page
• Assuming router.refresh() navigates to API route
• Believing nothing happens due to syntax error

4. Identify the error in this Next.js code snippet that tries to revalidate after mutation:

import { useRouter } from 'next/navigation';

export default function DeleteButton() {
  const router = useRouter;

  async function handleDelete() {
    await fetch('/api/delete', { method: 'DELETE' });
    router.refresh();
  }

  return Delete;
}

medium

A. Button onClick should be onSubmit

B. fetch method DELETE is invalid in Next.js

C. router is not called as a function, so router.refresh() fails

D. handleDelete should not be async

Solution

1. Step 1: Check router initialization

   Code uses const router = useRouter; missing parentheses, so router is a function reference, not the router object.

2. Step 2: Effect on router.refresh()

   Calling router.refresh() fails because router is not an object but a function reference.

3. Final Answer:

   router is not called as a function, so router.refresh() fails -> Option C

4. Quick Check:

   useRouter missing () causes error = D [OK]

Hint: Always call useRouter() with parentheses [OK]

Common Mistakes:

• Forgetting parentheses on useRouter()
• Thinking DELETE method is invalid
• Confusing onClick with onSubmit

5. You have a Next.js page showing a list of items fetched from the server. After adding a new item via a mutation API call, you want the list to update automatically. Which approach correctly ensures the list refreshes with the new data without a full page reload?

hard

A. Call router.push('/current-page') after mutation to reload the page

B. Call router.refresh() after mutation to revalidate and update data

C. Reload the browser window with window.location.reload()

D. Do nothing; the list updates automatically without any code

Solution

1. Step 1: Understand goal

   After mutation, the UI must show updated list without full reload or navigation.

2. Step 2: Evaluate options

   router.push('/current-page') navigates and reloads route, window.location.reload() reloads full page, and doing nothing won't update data.

3. Step 3: Correct method

   router.refresh() triggers Next.js to revalidate data and update UI efficiently.

4. Final Answer:

   Call router.refresh() after mutation to revalidate and update data -> Option B

5. Quick Check:

   Use router.refresh() to update data after mutation = B [OK]

Hint: Use router.refresh() to update data without full reload [OK]

Common Mistakes:

• Using router.push() causing unnecessary navigation
• Reloading full page losing state
• Assuming UI updates automatically without refresh