Skip to content

Docs: Add prefetching guide #80152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 10 commits into
base: canary
Choose a base branch
from
Draft

Conversation

delbaoliveira
Copy link
Contributor

@delbaoliveira delbaoliveira commented Jun 4, 2025

To do:

@ijjk ijjk added created-by: Next.js DevEx team PRs by the DX team. Documentation Related to Next.js' official documentation. labels Jun 4, 2025
Copy link

changeset-bot bot commented Jun 4, 2025

⚠️ No Changeset found

Latest commit: bd647d8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Comment on lines +201 to +204
### Disabling prefetching on hover

- How do you disable prefetch on hover? https://github.com/vercel/next.js/discussions/24437
- Use your own Ejected Link component
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Historically, this was a problem in pages router, because disabling prefetch, kept the on-hover behavior.

In this case, the root issue was "too many prefetches", that lead people to opt-into prefetch false, but, perhaps unexpectedly, still kept the on-hover issue.

In App Router, prefetch false, disables on-hover too. So that problem is solved. However, we have the opposite problem, so to speak. People who did want to disable prefetching on the viewport, but still prefetch on hover.

The proposal up above, to do a Hover-triggered prefetch ~ does cover the use case, so I think we can drops this third section altogether.

Suggested change
### Disabling prefetching on hover
- How do you disable prefetch on hover? https://github.com/vercel/next.js/discussions/24437
- Use your own Ejected Link component

Copy link
Contributor

github-actions bot commented Jun 6, 2025

All broken links are now fixed, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
created-by: Next.js DevEx team PRs by the DX team. Documentation Related to Next.js' official documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants