-
Notifications
You must be signed in to change notification settings - Fork 3
fix: prevent over-prefetching #341
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
Conversation
moonmeister
commented
Jun 26, 2025
- Fix navs and index pages from prefetching tons of content when rendered to the screen
- Fix Links from re-prefetching on every hover
…ts like archives and docs nav
|
Check out the recent updates to your Headless Platform preview environment:
Learn more about preview environments in our documentation. |
|
It seems Next link should be handling no re-prefetching...https://github.com/vercel/next.js/blob/canary/packages/next/src/client/link.tsx#L132-L187. I'm still unsure on why it's not working. |
|
Some more info: This is a Feature™️ of ISR. See: vercel/next.js#40268 TL;DRThe content "could have" changed in the background between hovers. In theory, these should return 304s and be relatively cheap. On the WPE hosting, that theory breaks down 😮💨 More below. TestingIn testing on Problem
My RealizationI had "No Cache" checked in dev tools. 🤦🏻 No, that's unchecked...304s are happening. The last remaining oddity is why no docs page other than Okay, I'm confused. I'm seeing pages vary between |
|
Check out the recent updates to your Headless Platform preview environment:
Learn more about preview environments in our documentation. |
|
Check out the recent updates to your Headless Platform preview environment:
Learn more about preview environments in our documentation. |
Fran-A-Dev
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM

