fix: resolve SSR hydration mismatch when ssrPath/ssrSearch not provided#549
Merged
fix: resolve SSR hydration mismatch when ssrPath/ssrSearch not provided#549
Conversation
|
|
6f96aa7 to
ac2a40f
Compare
When rendering on the client without ssrPath/ssrSearch props, usePathname and useSearch now use location.pathname and location.search as the SSR snapshot instead of defaulting to empty strings. This ensures the client-side hydration matches what was rendered on the server.
ac2a40f to
c7aceb5
Compare
size-limit report 📦
|
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.
Fixes #446
When
ssrPath/ssrSearchprops are not provided during client-side hydration, uselocation.pathnameandlocation.searchas the SSR snapshot instead of defaulting toempty strings. This ensures hydration matches the server-rendered output.