chore: bump @enbox/browser to ^0.3.9 (connect fan-out perf)#43
Merged
Conversation
Picks up @enbox/agent@0.6.8 transitively via @enbox/browser@0.3.9. @enbox/agent@0.6.8 (enboxorg/enbox#911) parallelizes endpoint fan-out in submitConnectResponse with bounded concurrency, eliminating the multi-second "Authorizing…" hang during the mobile wallet connect flow when the tenant has many DWN endpoints or the dapp requests many permissions. Verified: bun install, bun run lint (clean, --max-warnings 0), bun run build (clean), bun run test (312 pass / 0 fail across 26 test files). 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
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
Bumps `@enbox/browser` from `^0.3.8` to `^0.3.9`. The headline win is the transitive update of `@enbox/agent` to `0.6.8` (enboxorg/enbox#911) which parallelizes endpoint fan-out in `submitConnectResponse` with bounded concurrency, eliminating the multi-second "Authorizing…" hang during the mobile wallet connect flow.
Why this matters for nutsd
When the user scans a connect QR with their wallet, nutsd is waiting on `submitConnectResponse` to finish before it can show the PIN screen. With multiple permission grants and a tenant with multiple DWN endpoints under network load, the previous sequential fan-out caused multi-second hangs. The new bounded-concurrency fan-out keeps the spinner short while not stampeding DWN servers when either dimension grows large.
Server deployment
Not required. `@enbox/dwn-server` was not bumped (still at `0.1.3` on the registry). PR #911 was a pure client-side fix.
Test plan
Companion PR
`web-wallet`: bump full `@enbox/*` set to the 0.6.8 line.
Made with Cursor