Repository navigation
Clarify which pathname usePathname reads under rewrites - #100393
Merged
Merged
Conversation
github-actions
Bot
added
the
Documentation
Contributor
Tests PassedCommit: 9d45d75 |
icyJoseph
marked this pull request as ready for review
October 19, 2026 13:06
molebox
approved these changes
Oct 19, 2026
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
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.
Summary
Adjusts the "rewritten" wording used in the
usePathnamerewrites section and theblocking-prerender-client-hookerror page. The old text called the prerendered path the "source" and the browser URL the "rewritten" path, which reads backwards against thesource/destinationkeys in the rewrites config. It now says the server renders the rewrite destination (for example/blog/helloforapp/blog/[slug]/page.tsx) while the browser keeps the URL it requested, which is whatusePathname()returns on the client.