fix: re-check installed wallets after mount for late-injecting extensions#66
Merged
satoshai-dev merged 1 commit intomainfrom Apr 6, 2026
Merged
fix: re-check installed wallets after mount for late-injecting extensions#66satoshai-dev merged 1 commit intomainfrom
satoshai-dev merged 1 commit intomainfrom
Conversation
…ions Browser wallet extensions (Xverse, Leather, etc.) inject their globals into window at document_end/document_idle, which can race with React 19 hydration. The provider now stores detected wallets in state and re-checks once after mount so late-injecting extensions are picked up. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
satoshai-dev
added a commit
that referenced
this pull request
Apr 6, 2026
Instead of relying solely on the provider's render-time detection (which can miss extensions that inject after React hydration), useWallets now calls getStacksWallets() directly on every render. This ensures fresh detection at the point of consumption — by the time a user opens a connect-wallet drawer, extensions are detected. Reverts the provider-level useState/useEffect approach from #66 in favor of this simpler hook-level solution. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
3 tasks
satoshai-dev
added a commit
that referenced
this pull request
Apr 6, 2026
Instead of relying solely on the provider's render-time detection (which can miss extensions that inject after React hydration), useWallets now calls getStacksWallets() directly on every render. This ensures fresh detection at the point of consumption — by the time a user opens a connect-wallet drawer, extensions are detected. Reverts the provider-level useState/useEffect approach from #66 in favor of this simpler hook-level solution. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
satoshai-dev
added a commit
that referenced
this pull request
Apr 6, 2026
Instead of relying solely on the provider's render-time detection (which can miss extensions that inject after React hydration), useWallets now calls getStacksWallets() directly on every render. This ensures fresh detection at the point of consumption — by the time a user opens a connect-wallet drawer, extensions are detected. Reverts the provider-level useState/useEffect approach from #66 in favor of this simpler hook-level solution. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Summary
windowatdocument_end/document_idle, which can race with React 19 hydration on Next.js 16useEffect, so late-injecting extensions are picked upsetInstalled)Test plan
pnpm build)