Revalidation patterns in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is revalidation in Next.js?

Revalidation is the process of updating cached or statically generated pages after a set time or event, so users see fresh content without rebuilding the whole site.

beginner

What does the revalidate property do in Next.js getStaticProps?

It sets the number of seconds after which a page will be regenerated in the background when a request comes in, enabling Incremental Static Regeneration.

intermediate

Explain Incremental Static Regeneration (ISR) in Next.js.

ISR lets Next.js update static pages after build time by regenerating them on-demand in the background, so users get fast pages with fresh data.

intermediate

How does On-Demand Revalidation work in Next.js?

It allows you to manually trigger a page regeneration via an API route, so you can update pages immediately after data changes without waiting for the timer.

advanced

What is the difference between revalidate and cache-control headers in Next.js?

revalidate controls how often Next.js regenerates static pages, while cache-control headers control browser or CDN caching behavior for responses.

What does setting revalidate: 10 in getStaticProps do?

A Regenerates the page every 10 minutes

B Regenerates the page every 10 seconds on the server when requested

C Prevents the page from regenerating

D Caches the page in the browser for 10 seconds

The revalidate value is in seconds and tells Next.js to regenerate the page in the background if a request comes after 10 seconds.

Which Next.js feature allows manual triggering of page regeneration?

A On-Demand Revalidation

B Static Generation

C Server-Side Rendering

D Client-Side Rendering

On-Demand Revalidation lets you call an API route to manually trigger regeneration of static pages.

What happens if you don't set revalidate in getStaticProps?

A The page is generated once at build time and never updated automatically

B The page regenerates on every request

C The page is regenerated every second

D The page is deleted after build

Without revalidate, Next.js generates the page only once during build and serves that static page forever.

Which header controls browser caching behavior independently of Next.js revalidation?

A revalidate

B content-type

C cache-control

D etag

cache-control headers tell browsers and CDNs how long to cache responses.

Incremental Static Regeneration improves performance by:

A Disabling caching completely

B Rendering pages on every request

C Forcing full rebuilds on every change

D Serving static pages quickly and updating them in the background

ISR serves static pages fast and regenerates them in the background to keep content fresh.

Describe how Next.js uses the revalidate property to keep static pages fresh.

Think about how Next.js updates pages after build without slowing down users.

Explain the difference between automatic revalidation and on-demand revalidation in Next.js.

One happens by itself after some time, the other happens when you tell it to.

Practice

1. What does the revalidate export in Next.js control?

easy

A. How often a cached page updates after initial generation

B. The maximum number of pages to cache

C. The delay before a page is first generated

D. The priority of server-side rendering

Solution

1. Step 1: Understand the role of revalidate

   The revalidate export sets the time in seconds for Next.js to update a cached page after it was first generated.

2. Step 2: Compare options with this behavior

   Only How often a cached page updates after initial generation correctly describes this update frequency control. Other options describe unrelated concepts.

3. Final Answer:

   How often a cached page updates after initial generation -> Option A

4. Quick Check:

   Revalidate controls update frequency = D [OK]

Hint: Remember revalidate sets cache update time in seconds [OK]

Common Mistakes:

• Confusing revalidate with cache size
• Thinking revalidate delays first page generation
• Mixing revalidate with rendering priority

2. Which of the following is the correct syntax to set a page to revalidate every 60 seconds in Next.js?

easy

A. export revalidate = 60;

B. export const revalidate = 60;

C. const revalidate = 60 export;

D. export const revalidate(60);

Solution

1. Step 1: Recall correct export syntax in Next.js

   To export a constant, the syntax is export const name = value;.

2. Step 2: Match this with revalidate usage

   export const revalidate = 60; matches this pattern exactly. Other options have syntax errors or misplaced keywords.

3. Final Answer:

   export const revalidate = 60; -> Option B

4. Quick Check:

   Correct export syntax = A [OK]

Hint: Use 'export const' to export revalidate value [OK]

Common Mistakes:

• Omitting 'const' keyword
• Using parentheses incorrectly
• Placing export keyword after variable

3. Given this Next.js page code snippet:

export const revalidate = 10;

export default function Page() {
  return <div>Time: {Date.now()}</div>;
}

What will happen if you visit this page multiple times within 10 seconds?

medium

A. The page updates the timestamp on every visit immediately

B. The page never updates after the first visit

C. The page throws an error because Date.now() is not allowed

D. The page shows the same timestamp for 10 seconds before updating

Solution

1. Step 1: Understand revalidate timing effect

   With revalidate = 10, Next.js caches the page and only regenerates it after 10 seconds.

2. Step 2: Predict page behavior on multiple visits

   Within 10 seconds, the cached page is served, so the timestamp stays the same. After 10 seconds, it updates.

3. Final Answer:

   The page shows the same timestamp for 10 seconds before updating -> Option D

4. Quick Check:

   Revalidate caches page for 10 seconds = B [OK]

Hint: Revalidate delays page update by set seconds [OK]

Common Mistakes:

• Assuming Date.now() updates on every visit
• Thinking revalidate disables page updates
• Confusing revalidate with client-side rendering

4. You wrote this code in a Next.js page:

export const revalidate = '30';

export default function Page() {
  return <div>Hello</div>;
}

What is the problem with this code?

medium

A. revalidate must be a number, not a string

B. Page component must be async to use revalidate

C. You cannot export revalidate in a page component

D. The return statement is missing parentheses

Solution

1. Step 1: Check the type of revalidate value

   The revalidate export expects a number representing seconds, not a string.

2. Step 2: Identify the error caused by wrong type

   Using a string will cause Next.js to ignore or error on revalidation timing.

3. Final Answer:

   revalidate must be a number, not a string -> Option A

4. Quick Check:

   revalidate requires number type = A [OK]

Hint: Use number, not quotes, for revalidate seconds [OK]

Common Mistakes:

• Using quotes around the number
• Thinking revalidate needs async function
• Misunderstanding export rules

5. You want a Next.js page to show fresh data but also improve performance by caching for 5 minutes. Which revalidation pattern should you use?

export const revalidate = ?;

Choose the best value and explain why.

hard

A. 60, to update every minute for fresher data

B. 0, to disable caching and always fetch fresh data

C. 300, because 300 seconds equals 5 minutes, balancing freshness and caching

D. Infinity, to cache forever and never update

Solution

1. Step 1: Convert 5 minutes to seconds

   5 minutes equals 300 seconds, so revalidate should be set to 300.

2. Step 2: Understand caching vs freshness tradeoff

   Setting revalidate to 300 caches the page for 5 minutes, improving performance but still updating regularly.

3. Step 3: Evaluate other options

   0 disables caching (no performance gain), 60 updates too often, Infinity never updates (stale data).

4. Final Answer:

   300, because 300 seconds equals 5 minutes, balancing freshness and caching -> Option C

5. Quick Check:

   5 minutes = 300 seconds revalidate [OK]

Hint: Set revalidate to seconds matching desired cache time [OK]

Common Mistakes:

• Using 0 thinking it improves performance
• Choosing too short or too long revalidate values
• Confusing minutes with seconds