archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/packages/next/cache.js

22 lines
885 B
JavaScript
Raw Normal View History

Update revalidate handling for app (#49062) This updates revalidate handling for app and moves some exports from `next/server` to `next/cache` x-ref: [slack thread](https://vercel.slack.com/archives/C042LHPJ1NX/p1682535961644979?thread_ts=1682368724.384619&cid=C042LHPJ1NX) ---------
2023-05-02 17:19:02 +02:00
const cacheExports = {
unstable_cache: require('next/dist/server/web/spec-extension/unstable-cache')
.unstable_cache,
Update cache methods for app dir (#49165) This ensures we match behavior local and deployed and also cleans up naming of the methods. ---------
2023-05-03 22:21:58 +02:00
revalidateTag: require('next/dist/server/web/spec-extension/revalidate-tag')
.revalidateTag,
revalidatePath: require('next/dist/server/web/spec-extension/revalidate-path')
.revalidatePath,
cache: add unstable_noStore API (#56930) 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(...); } ```
2023-10-17 16:52:46 +02:00
unstable_noStore:
require('next/dist/server/web/spec-extension/unstable-no-store')
.unstable_noStore,
Update revalidate handling for app (#49062) This updates revalidate handling for app and moves some exports from `next/server` to `next/cache` x-ref: [slack thread](https://vercel.slack.com/archives/C042LHPJ1NX/p1682535961644979?thread_ts=1682368724.384619&cid=C042LHPJ1NX) ---------
2023-05-02 17:19:02 +02:00
}
// 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
Update cache methods for app dir (#49165) This ensures we match behavior local and deployed and also cleans up naming of the methods. ---------
2023-05-03 22:21:58 +02:00
exports.revalidatePath = cacheExports.revalidatePath
exports.revalidateTag = cacheExports.revalidateTag
cache: add unstable_noStore API (#56930) 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(...); } ```
2023-10-17 16:52:46 +02:00
exports.unstable_noStore = cacheExports.unstable_noStore
Reference in a new issue Copy permalink