@@ -91,7 +91,7 @@ When a request is made to a path that hasn’t been generated, Next.js will serv
...
@@ -91,7 +91,7 @@ When a request is made to a path that hasn’t been generated, Next.js will serv
If you set a `revalidate` time of `60`, all visitors will see the same generated version of your site for one minute. The only way to invalidate the cache is from someone visiting that page after the minute has passed.
If you set a `revalidate` time of `60`, all visitors will see the same generated version of your site for one minute. The only way to invalidate the cache is from someone visiting that page after the minute has passed.
Starting with `v12.1.0`, Next.js supports on-demand Incremental Static Regeneration to manually purge the Next.js cache for a specific page. This makes it easier to update your site when:
Starting with `v12.1.0`, Next.js supports On-Demand Incremental Static Regeneration to manually purge the Next.js cache for a specific page. This makes it easier to update your site when:
- Content from your headless CMS is created or updated
- Content from your headless CMS is created or updated
[View our demo](https://on-demand-isr.vercel.app) to see on-demand revalidation in action and provide feedback.
[View our demo](https://on-demand-isr.vercel.app) to see on-demand revalidation in action and provide feedback.
### Testing on-demand ISR during development
### Testing on-Demand ISR during development
When running locally with `next dev`, `getStaticProps` is invoked on every request. To verify your on-demand ISR configuration is correct, you will need to create a [production build](/docs/api-reference/cli.md#build) and start the [production server](/docs/api-reference/cli.md#production):
When running locally with `next dev`, `getStaticProps` is invoked on every request. To verify your on-demand ISR configuration is correct, you will need to create a [production build](/docs/api-reference/cli.md#build) and start the [production server](/docs/api-reference/cli.md#production):