chore: bump @enbox/browser to ^0.3.10 (Authorizing… spinner fix)#44
Merged
Conversation
Picks up enboxorg/enbox#914 transitively via @enbox/browser, which now depends on @enbox/agent 0.7.0 + @enbox/dwn-clients 0.4.0. The fix is client-side in the wallet (skipping the redundant remote ProtocolsConfigure send during submitConnectResponse + per-request AbortSignal.timeout on every connect-flow RPC), so dapps just need to be on the matching browser bundle. @enbox/browser 0.3.9 -> 0.3.10 Lint / vitest (312 tests) / build all pass. Made-with: Cursor
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
Picks up enboxorg/enbox#914 transitively via
@enbox/browser, which now depends on@enbox/agent0.7.0 +@enbox/dwn-clients0.4.0.The fix is client-side in the wallet (the agent skips the redundant remote
ProtocolsConfiguresend duringsubmitConnectResponse, and every connect-flowagent.rpc.sendDwnRequestis capped by a 10 sAbortSignal.timeoutplumbed through the newDwnRpcRequest.signalfield). Dapps just need to be on the matching browser bundle so the@enbox/authwalletConnectclient uses the same package versions.Version bump
@enbox/browser(Transitively pulls in
@enbox/agent0.7.0,@enbox/dwn-clients0.4.0,@enbox/auth0.6.32.)Test plan
bun install— cleanbun run lint— clean (max-warnings 0)bun run test— 312 / 312 passbun run build— cleanMade with Cursor