Unverified Commit 7bb6730b authored by Aurora Scharff's avatar Aurora Scharff Committed by GitHub

docs: clarify hover prefetching with Partial Prefetching (#99665)

## Summary

- Link to the Partial Prefetching adoption guide and clarify how the
existing hover-triggered `<Link>` example changes
- Use `auto` before intent to preserve the shared App Shell prefetch,
then use `true` to resolve cached URL-specific content
- Explain that `prefetch={false}` also disables the App Shell prefetch

## Verification

- `pnpm prettier --with-node-modules --ignore-path .prettierignore
--write docs/01-app/02-guides/prefetching.mdx
docs/01-app/02-guides/optimizing-prefetching.mdx`
- `pnpm exec eslint --config eslint.config.mjs --fix
docs/01-app/02-guides/prefetching.mdx
docs/01-app/02-guides/optimizing-prefetching.mdx`
- `git diff --check origin/canary...HEAD`

<!-- NEXT_JS_LLM -->
parent 035c4da5
...@@ -151,7 +151,9 @@ export function HoverPrefetchLink({ ...@@ -151,7 +151,9 @@ export function HoverPrefetchLink({
} }
``` ```
`prefetch={null}` restores default (static) prefetching once the user shows intent. `prefetch={null}` restores default prefetching once the user shows intent.
With [Partial Prefetching](/docs/app/guides/adopting-partial-prefetching), use `prefetch={active ? true : 'auto'}` instead. The `'auto'` value keeps the shared App Shell prefetched before the user shows intent, while `true` resolves cached URL-specific content before navigation after they do. Using `false` before intent disables the App Shell prefetch.
### Extending or ejecting link ### Extending or ejecting link
......
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