Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://nextjs.org/docs/app/api-reference/functions/unstable_noStore below:

Website Navigation

• Previous

  unstable_cache

• Next

  unstable_rethrow

Functions: unstable_noStore | Next.js

This is a legacy API and no longer recommended. It's still supported for backward compatibility.

In version 15, we recommend using 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.

import { unstable_noStore as noStore } 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 will not opt out of static generation. Instead, it will defer to the cache configuration to determine whether to cache the result or not.

If you prefer not to pass additional options to fetch, like cache: 'no-store', next: { revalidate: 0 } or in cases where fetch is not available, you can use noStore() as a replacement for all of these use cases.

import { unstable_noStore as noStore } from 'next/cache';
 
export default async function ServerComponent() {
  noStore();
  const result = await db.query(...);
  ...
}

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4