Opting out of caching in NextJS - Step-by-Step Execution

Concept Flow - Opting out of caching

Request received

↓

Check cache policy

↓

Cache

↓

Send response

When a request comes in, Next.js checks if caching is allowed. If opted out, it fetches fresh data every time.

Execution Sample

NextJS

export const dynamic = 'force-dynamic';

export default function Page() {
  return <h1>Fresh content every time</h1>;
}

This Next.js page disables caching to always serve fresh content.

Execution Table

Step	Action	Cache Policy	Data Source	Response Sent
1	Request received	Check dynamic export	N/A	N/A
2	dynamic = 'force-dynamic' detected	No caching	Fetch fresh data	N/A
3	Render page with fresh data	No caching	Fresh data	<h1>Fresh content every time</h1>
4	Send response to client	No caching	Fresh data	<h1>Fresh content every time</h1>
5	Next request arrives	Repeat steps 1-4	Always fresh	Always fresh response

💡 Caching is disabled by dynamic = 'force-dynamic', so fresh data is fetched every request.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
dynamic	undefined	'force-dynamic'	'force-dynamic'	'force-dynamic'	'force-dynamic'
cacheAllowed	true	false	false	false	false
dataSource	N/A	fresh fetch	fresh data	fresh data	fresh data
responseContent	N/A	N/A	<h1>Fresh content every time</h1>	<h1>Fresh content every time</h1>	<h1>Fresh content every time</h1>

Key Moments - 2 Insights

Why does the page fetch fresh data every time instead of using cache?

Because the dynamic export is set to 'force-dynamic' (see execution_table step 2), Next.js disables caching and fetches fresh data on every request.

What happens if we remove the dynamic export?

Next.js will use default caching behavior, so the page might serve cached content instead of fresh data (not shown in this trace).

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the data source used?

A Cached data

B Fresh data fetched

C No data

D Static pre-rendered data

💡 Hint

Check the 'Data Source' column at step 3 in execution_table.

At which step is the cache policy determined to disable caching?

A Step 1

B Step 4

C Step 2

D Step 5

💡 Hint

Look at the 'Cache Policy' column in execution_table to find when 'No caching' is set.

If we change dynamic to 'force-static', how would the response behavior change?

A Page caches data and serves cached content when possible

B Page throws an error

C Page always fetches fresh data

D Page disables rendering

💡 Hint

Refer to variable_tracker 'dynamic' variable and understand how 'force-dynamic' disables caching.

Concept Snapshot

Next.js lets you control caching with the dynamic export.
Set dynamic = 'force-dynamic' to disable caching.
This makes Next.js fetch fresh data every request.
Useful for pages needing always up-to-date content.
Without it, Next.js may cache and reuse data.
Remember: disabling cache can affect performance.

Full Transcript

In Next.js, you can opt out of caching by exporting a special variable called dynamic with the value 'force-dynamic'. When a request comes in, Next.js checks this setting. If it sees 'force-dynamic', it skips caching and fetches fresh data every time. This means the page always shows the latest content. The example code exports dynamic = 'force-dynamic' and returns a simple heading. The execution table shows each step: receiving the request, detecting the no-cache policy, fetching fresh data, rendering the page, and sending the response. Variables like dynamic and cacheAllowed track this behavior. Key moments include understanding why fresh data is fetched and what happens if the dynamic export is removed. The quiz tests your understanding of data source, cache policy timing, and effects of changing dynamic. Remember, opting out of caching ensures fresh content but may reduce performance due to repeated data fetching.

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