@@ -102,13 +102,13 @@ Set the cache tags of a resource. Data can then be revalidated on-demand using [
...
@@ -102,13 +102,13 @@ Set the cache tags of a resource. Data can then be revalidated on-demand using [
## Troubleshooting
## Troubleshooting
## Fetch `cache: 'no-store'` not showing fresh data in development
### Fetch `cache: 'no-store'` not showing fresh data in development
Next.js caches `fetch` responses in Server Components across Hot Module Replacement (HMR) in local development for faster responses and to reduce costs for billed API calls.
Next.js caches `fetch` responses in Server Components across Hot Module Replacement (HMR) in local development for faster responses and to reduce costs for billed API calls.
By default, the [HMR cache](docs/app/api-reference/next-config-js/servercomponentshmrcache) applies to all fetch requests, including those with the `cache: 'no-store'` option. This means uncached requests will not show fresh data between HMR refreshes. However, the cache will be cleared on navigation or full-page reloads.
By default, the [HMR cache](/docs/app/api-reference/next-config-js/serverComponentsHmrCache) applies to all fetch requests, including those with the `cache: 'no-store'` option. This means uncached requests will not show fresh data between HMR refreshes. However, the cache will be cleared on navigation or full-page reloads.
See the [`serverComponentsHmrCache`](docs/app/api-reference/next-config-js/servercomponentshmrcache) docs for more information.
See the [`serverComponentsHmrCache`](/docs/app/api-reference/next-config-js/serverComponentsHmrCache) docs for more information.