| --- |
| title: unstable_noStore |
| description: API Reference for the unstable_noStore function. |
| version: legacy |
| --- |
|
|
| **In version 15, we recommend using [`connection`](/docs/app/api-reference/functions/connection) instead of `unstable_noStore`.** |
|
|
| `unstable_noStore` can be used to declaratively opt out of static rendering and indicate a particular component should not be cached. |
|
|
| ```jsx |
| import from 'next/cache'; |
|
|
| export default async function ServerComponent() |
| noStore(); |
| const result = await db.query(...); |
| ... |
| } |
| ``` |
|
|
| > **Good to know**: |
| > |
| > - `unstable_noStore` is equivalent to `cache: 'no-store'` on a `fetch` |
| > - `unstable_noStore` is preferred over `export const dynamic = 'force-dynamic'` as it is more granular and can be used on a per-component basis |
|
|
| - Using `unstable_noStore` inside [`unstable_cache`](/docs/app/api-reference/functions/unstable_cache) will not opt out of static generation. Instead, it will defer to the cache configuration to determine whether to cache the result or not. |
|
|
| ## Usage |
|
|
| If you prefer not to pass additional options to `fetch`, like `cache: 'no-store'`, `next: ` or in cases where `fetch` is not available, you can use `noStore()` as a replacement for all of these use cases. |
|
|
| ```jsx |
| import from 'next/cache'; |
|
|
| export default async function ServerComponent() |
| noStore(); |
| const result = await db.query(...); |
| ... |
| } |
| ``` |
|
|
| ## Version History |
|
|
| | Version | Changes | |
| | --------- | ----------------------------------------------- | |
| | `v15.0.0` | `unstable_noStore` deprecated for `connection`. | |
| | `v14.0.0` | `unstable_noStore` introduced. | |
|
|
