Revalidation patterns in NextJS - Mini Project: Build & Apply

Next.js Revalidation Patterns

📖 Scenario: You are building a simple blog homepage using Next.js. The blog posts data changes occasionally, so you want to make sure the page updates without rebuilding the entire site every time.

🎯 Goal: Create a Next.js page that fetches blog posts data and uses revalidate to update the page every 10 seconds automatically.

📋 What You'll Learn

Create a posts array with three blog post objects, each having id, title, and content fields.

Add a revalidateTime variable set to 10 (seconds).

Write an async function getStaticProps that returns the posts data and sets revalidate to revalidateTime.

Create a default exported React functional component HomePage that receives posts as props and renders the titles in an unordered list.

💡 Why This Matters

🌍 Real World

Many websites need to update content regularly without full rebuilds. Next.js revalidation lets you keep pages fresh with minimal server load.

💼 Career

Understanding revalidation patterns is important for building fast, scalable React apps with Next.js that handle dynamic data efficiently.

1

Create the blog posts data array

Create a constant array called posts with exactly three objects. Each object must have these exact keys and values: { id: 1, title: 'First Post', content: 'This is the first post.' }, { id: 2, title: 'Second Post', content: 'This is the second post.' }, and { id: 3, title: 'Third Post', content: 'This is the third post.' }.

NextJS

# Your code here

Hint

Use const posts = [ ... ] with three objects inside.

2

Add the revalidation time variable

Create a constant called revalidateTime and set it to the number 10.

NextJS

const posts = [
  { id: 1, title: 'First Post', content: 'This is the first post.' },
  { id: 2, title: 'Second Post', content: 'This is the second post.' },
  { id: 3, title: 'Third Post', content: 'This is the third post.' }
];

# Your code here

Hint

Use const revalidateTime = 10; to set the revalidation interval.

3

Write the getStaticProps function with revalidation

Write an async function called getStaticProps that returns an object with props containing the posts array, and a revalidate property set to revalidateTime.

NextJS

const posts = [
  { id: 1, title: 'First Post', content: 'This is the first post.' },
  { id: 2, title: 'Second Post', content: 'This is the second post.' },
  { id: 3, title: 'Third Post', content: 'This is the third post.' }
];

const revalidateTime = 10;

# Your code here

Hint

Use export async function getStaticProps() { return { props: { posts }, revalidate: revalidateTime } }.

4

Create the HomePage component to display posts

Create a default exported React functional component called HomePage that accepts posts as a prop. Inside, return a <main> element containing an unordered list <ul>. Map over posts and render each post's title inside a <li> with a unique key set to the post's id.

NextJS

const posts = [
  { id: 1, title: 'First Post', content: 'This is the first post.' },
  { id: 2, title: 'Second Post', content: 'This is the second post.' },
  { id: 3, title: 'Third Post', content: 'This is the third post.' }
];

const revalidateTime = 10;

export async function getStaticProps() {
  return {
    props: { posts },
    revalidate: revalidateTime
  };
}

# Your code here

Hint

Use export default function HomePage({ posts }) { return ( <main><ul>{posts.map(post => <li key={post.id}>{post.title}</li>)}</ul></main> ) }.

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