451a54cb2e
This PR introduces a new API, `unstable_noStore`, which will allow users to declaratively opt out of caching anywhere during static generation in the same way that you can specify `cache: 'no-store'` on a fetch call in Next.js.
An important caveat and difference from just calling `cookies()` to opt-out of static generation is that this won't opt you out when called from within `unstable_cache` and instead defers to the cache configuration to it.
```
import {unstable_noStore as noStore} from 'next/cache';
export default async function Component() {
noStore();
const result = await db.query(...);
}
```
21 lines
885 B
JavaScript
21 lines
885 B
JavaScript
const cacheExports = {
|
|
unstable_cache: require('next/dist/server/web/spec-extension/unstable-cache')
|
|
.unstable_cache,
|
|
revalidateTag: require('next/dist/server/web/spec-extension/revalidate-tag')
|
|
.revalidateTag,
|
|
revalidatePath: require('next/dist/server/web/spec-extension/revalidate-path')
|
|
.revalidatePath,
|
|
unstable_noStore:
|
|
require('next/dist/server/web/spec-extension/unstable-no-store')
|
|
.unstable_noStore,
|
|
}
|
|
|
|
// https://nodejs.org/api/esm.html#commonjs-namespaces
|
|
// When importing CommonJS modules, the module.exports object is provided as the default export
|
|
module.exports = cacheExports
|
|
|
|
// make import { xxx } from 'next/server' work
|
|
exports.unstable_cache = cacheExports.unstable_cache
|
|
exports.revalidatePath = cacheExports.revalidatePath
|
|
exports.revalidateTag = cacheExports.revalidateTag
|
|
exports.unstable_noStore = cacheExports.unstable_noStore
|