fix: hydration mismatch in NostrIdentityProvider - #34
Merged
Conversation
…mismatch The typeof window branch caused the server to render a different component tree than the client. Replaced with a mounted flag that ensures both server and first client render use capability: null. sessionStorage is read in a useEffect after mount, which then re-renders with the real capability.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…ionStorage hydration
comwanga
marked this pull request as ready for review
August 8, 2026 17:18
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.
The
typeof windowbranch inNostrIdentityProvidercaused the server to render a different component tree than the client, triggering a React hydration mismatch on the agent page.Fix: Removed the conditional render branch and replaced it with a
mountedstate flag. Both server and first client render now usecapability: null. The actual capability is loaded fromsessionStoragein auseEffectafter mount, which then re-renders.