Opting out of caching in NextJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to disable caching for a Next.js Server Component.

NextJS

export const revalidate = [1];

export default function Page() {
  return <h1>No caching here!</h1>;
}

Drag options to blanks, or click blank then click option'

A0

Bfalse

Ctrue

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'false' instead of 0 does not disable caching.

Setting 'true' enables caching, not disables.

Setting revalidate = 0 tells Next.js not to cache the page and always fetch fresh data.

2fill in blank

medium

Complete the code to disable caching for a Next.js API route.

NextJS

export const GET = async () => {
  return new Response('No cache', {
    headers: {
      'Cache-Control': [1]
    }
  });
};

Drag options to blanks, or click blank then click option'

A'public, max-age=3600'

B'no-store'

C'private, max-age=0'

D'max-age=0'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'max-age=0' may still allow some caching.

Using 'public' allows caching, which is not desired here.

Using 'no-store' in the Cache-Control header tells the browser and CDN not to cache the response.

3fill in blank

hard

Fix the error in disabling caching for a Next.js page by completing the export.

NextJS

export const [1] = 0;

export default function Page() {
  return <p>Fresh data always</p>;
}

Drag options to blanks, or click blank then click option'

AnoCache

Bcache

Crevalidate

DcacheControl

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'cache' or 'cacheControl' are not recognized exports.

Using 'noCache' is not a valid Next.js export.

The correct export to control caching in Next.js pages is revalidate.

4fill in blank

hard

Fill both blanks to disable caching and set a custom header in a Next.js API route.

NextJS

export const GET = async () => {
  return new Response('No cache', {
    headers: {
      'Cache-Control': [1],
      'Pragma': [2]
    }
  });
};

Drag options to blanks, or click blank then click option'

A'no-store'

B'no-cache'

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up 'no-store' and 'no-cache' values.

Omitting the 'Pragma' header for older clients.

Setting 'Cache-Control' to 'no-store' disables caching, and 'Pragma' to 'no-cache' is for backward compatibility with HTTP/1.0 caches.

5fill in blank

hard

Fill all three blanks to create a Next.js page that opts out of caching and fetches fresh data.

NextJS

export const [1] = [2];

export default async function Page() {
  const res = await fetch('https://api.example.com/data', { cache: [3] });
  const data = await res.json();
  return <pre>{JSON.stringify(data, null, 2)}</pre>;
}

Drag options to blanks, or click blank then click option'

Arevalidate

B0

C'no-store'

D'force-cache'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'force-cache' in fetch options caches data.

Setting revalidate to true or false instead of 0.

Setting revalidate = 0 disables Next.js page caching. Passing { cache: 'no-store' } to fetch disables fetch caching, ensuring fresh data.

Practice

1. In Next.js, how do you disable caching for a page to always fetch fresh content?

easy

A. Set cache: false in next.config.js

B. Use getStaticProps without any options

C. Add no-cache header in _app.js

D. Set export const revalidate = 0; in the page file

Solution

1. Step 1: Understand Next.js caching control

   Next.js uses the revalidate export to control caching duration for static pages.

2. Step 2: Disable caching by setting revalidate to zero

   Setting revalidate = 0 tells Next.js to never cache and always fetch fresh data.

3. Final Answer:

   Set export const revalidate = 0; in the page file -> Option D

4. Quick Check:

   revalidate = 0 disables caching [OK]

Hint: Remember: revalidate = 0 means no caching [OK]

Common Mistakes:

• Confusing revalidate with cache settings in config
• Trying to disable caching via headers only
• Omitting the export keyword for revalidate

2. Which of the following is the correct syntax to disable caching in a Next.js page?

easy

A. export const revalidate = '0';

B. export const revalidate = 0;

C. const revalidate = 0;

D. export default revalidate = 0;

Solution

1. Step 1: Check correct export syntax

   In Next.js, caching control requires exporting a constant named revalidate.

2. Step 2: Use number zero without quotes

   The value must be a number 0, not a string, and must be exported properly.

3. Final Answer:

   export const revalidate = 0; -> Option B

4. Quick Check:

   Correct export with number zero disables caching [OK]

Hint: Use number 0 without quotes and export it [OK]

Common Mistakes:

• Using string '0' instead of number 0
• Not exporting the variable
• Using default export incorrectly

3. Given this Next.js page code snippet, what will be the caching behavior?

export const revalidate = 0;

export default function Page() {
  return <h1>Fresh Content</h1>;
}

medium

A. The page is never cached and always fetches fresh content

B. The page is cached and refreshed every 10 seconds

C. The page is cached indefinitely

D. The page throws a runtime error due to invalid revalidate value

Solution

1. Step 1: Identify the revalidate value

   The code sets revalidate = 0, which disables caching.

2. Step 2: Understand effect on page behavior

   With caching disabled, the page always fetches fresh content on each request.

3. Final Answer:

   The page is never cached and always fetches fresh content -> Option A

4. Quick Check:

   revalidate = 0 means no caching [OK]

Hint: revalidate 0 means always fresh, no cache [OK]

Common Mistakes:

• Assuming default caching applies
• Thinking 0 means cache forever
• Confusing with ISR default timing

4. You wrote this code to disable caching but the page still caches:

const revalidate = 0;

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

What is the error?

medium

A. Missing export keyword for revalidate

B. revalidate cannot be zero

C. Page component must be a class

D. Return statement syntax is incorrect

Solution

1. Step 1: Check revalidate declaration

   The variable revalidate must be exported to affect caching.

2. Step 2: Identify missing export

   Without export, Next.js ignores the variable and uses default caching.

3. Final Answer:

   Missing export keyword for revalidate -> Option A

4. Quick Check:

   revalidate must be exported to disable caching [OK]

Hint: Always export revalidate to control caching [OK]

Common Mistakes:

• Forgetting to export revalidate
• Thinking revalidate must be non-zero
• Confusing functional and class components

5. You want a Next.js page to always show fresh data but only disable caching for authenticated users. Which approach correctly opts out of caching only for them?

hard

A. Set revalidate = 0 inside getStaticProps conditionally

B. Set export const revalidate = 0; unconditionally in the page file

C. Use server-side rendering with export const dynamic = 'force-dynamic'; and check auth inside

D. Add Cache-Control: no-store header in _app.js for all requests

Solution

1. Step 1: Understand conditional caching needs

   Disabling caching only for authenticated users requires dynamic rendering based on request context.

2. Step 2: Use dynamic rendering with auth check

   Setting export const dynamic = 'force-dynamic'; forces server-side rendering, allowing auth checks per request.

3. Step 3: Why other options fail

   Set export const revalidate = 0; unconditionally in the page file disables caching for all users; Set revalidate = 0 inside getStaticProps conditionally is invalid because revalidate is static; Add Cache-Control: no-store header in _app.js for all requests affects all requests globally.

4. Final Answer:

   Use server-side rendering with export const dynamic = 'force-dynamic'; and check auth inside -> Option C

5. Quick Check:

   Dynamic rendering enables conditional caching [OK]

Hint: Use dynamic rendering to control caching per user [OK]

Common Mistakes:

• Trying to set revalidate conditionally inside getStaticProps
• Disabling caching globally instead of per user
• Misusing cache headers in _app.js