Unverified Commit b1eba13d authored by Pranav's avatar Pranav Committed by GitHub

docs: remove incorrect statement that force-cache is the default for … (#95235)

Fixes #62875

Removes the incorrect comment that `force-cache` is the default and can
be omitted.
In Next.js 15, fetch requests are no longer cached by default, so this
statement
was misleading for developers migrating to the App Router.

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Signed commits

- This repository requires verified commit signatures on protected
branches.
- If this pull request is blocked for unsigned commits, re-sign the
commits and force-push the branch.
- A `Signed-off-by` line in the commit message is not enough.


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->
parent 614443ce
......@@ -525,18 +525,20 @@ The `pages` directory uses `getServerSideProps` and `getStaticProps` to fetch da
```tsx filename="app/page.tsx" switcher
export default async function Page() {
// This request should be cached until manually invalidated.
// Opt into the Next.js Data Cache for this request.
// The cached response can be reused across requests and revalidated on demand.
// Similar to `getStaticProps`.
// `force-cache` is the default and can be omitted.
const staticData = await fetch(`https://...`, { cache: 'force-cache' })
const cachedData = await fetch('https://...', { cache: 'force-cache' })
// This request should be refetched on every request.
// Opt out of caching for this request.
// Next.js fetches this from the data source on every request.
// This is the default fetch behavior.
// Similar to `getServerSideProps`.
const dynamicData = await fetch(`https://...`, { cache: 'no-store' })
const uncachedData = await fetch('https://...', { cache: 'no-store' })
// This request should be cached with a lifetime of 10 seconds.
// Cache this request, but revalidate it at most every 10 seconds.
// Similar to `getStaticProps` with the `revalidate` option.
const revalidatedData = await fetch(`https://...`, {
const revalidatedData = await fetch('https://...', {
next: { revalidate: 10 },
})
......@@ -546,18 +548,20 @@ export default async function Page() {
```jsx filename="app/page.js" switcher
export default async function Page() {
// This request should be cached until manually invalidated.
// Opt into the Next.js Data Cache for this request.
// The cached response can be reused across requests and revalidated on demand.
// Similar to `getStaticProps`.
// `force-cache` is the default and can be omitted.
const staticData = await fetch(`https://...`, { cache: 'force-cache' })
const cachedData = await fetch('https://...', { cache: 'force-cache' })
// This request should be refetched on every request.
// Opt out of caching for this request.
// Next.js fetches this from the data source on every request.
// This is the default fetch behavior.
// Similar to `getServerSideProps`.
const dynamicData = await fetch(`https://...`, { cache: 'no-store' })
const uncachedData = await fetch('https://...', { cache: 'no-store' })
// This request should be cached with a lifetime of 10 seconds.
// Cache this request, but revalidate it at most every 10 seconds.
// Similar to `getStaticProps` with the `revalidate` option.
const revalidatedData = await fetch(`https://...`, {
const revalidatedData = await fetch('https://...', {
next: { revalidate: 10 },
})
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment