Repository navigation
fix: restore default prefetching for internal links - #173
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
f0rr0
changed the title
f0rr0
force-pushed
the
f0rr0/prefetch-writing-posts
branch
from
September 28, 2026 14:21
c393ebf to
2f1e248
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Writing links on Home and Writing and the “See what I’m shipping” link on Tokens disabled Next.js prefetching, leaving page downloads until a click. Remove both opt-outs and use the framework defaults. A repository-wide navigation audit found no other prefetch opt-outs; remaining native anchors are external links, downloads, assets, or in-page anchors.
Validation: reproduced a 729 ms article navigation on the live site with no article prefetch. Local production browser checks confirmed prefetch and 81–96 ms navigation with no article payload or JavaScript fetch after the click, from Writing at desktop width and Home at mobile width. These timings come from different environments. All 13 posts remain statically generated, so prefetching them does not query Supabase; Work retains its existing cache policy.
Production build, six article/SEO/share-image tests, fourteen token-details tests, lint, Knip, and typecheck pass.