npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@bosonprotocol/x402-client-browser

v0.2.1

Published

Browser-environment adapters for the Boson Protocol x402 buyer-side SDK — wraps a viem WalletClient or a raw EIP-1193 provider (e.g. window.ethereum) as an X402bClient Signer.

Downloads

1,234

Readme

@bosonprotocol/x402-client-browser

Browser-environment adapters for x402B — Boson Protocol's implementation of the x402-escrow-schema.

This package wraps a browser wallet — either a viem WalletClient or a raw EIP-1193 provider (e.g. window.ethereum) — as the Signer interface that createX402bClient expects. Pair it with @bosonprotocol/x402-client-fetch for the 402-retry plumbing in a browser app.

Status

Pre-release skeleton. The adapter-specific exports are signerFromWalletClient and signerFromEip1193; the rest of the public API — createX402bClient, error classes, client.handle402, client.signAction, client.parsePaymentResponse, and the configuration types — is re-exported verbatim from @bosonprotocol/x402-client, so a single install of this package covers the common browser case.

Install

pnpm add @bosonprotocol/x402-client-browser
# or: npm install @bosonprotocol/x402-client-browser

Usage — viem WalletClient

import { createWalletClient, custom } from "viem";
import { base } from "viem/chains";
import {
  createX402bClient,
  signerFromWalletClient,
} from "@bosonprotocol/x402-client-browser";

const walletClient = createWalletClient({
  chain: base,
  transport: custom(window.ethereum!),
});

// If the wallet client was created without a bound account, pass one
// explicitly via `{ account }`.
const [address] = await walletClient.getAddresses();

const client = createX402bClient({
  signer: signerFromWalletClient(walletClient, { account: address }),
  tokenDomainResolver: async (asset, chainId) => ({
    name: "USD Coin",
    version: "2",
    chainId,
    verifyingContract: asset,
  }),
});

Usage — raw EIP-1193 provider

signerFromEip1193 resolves the signing address lazily on each call. By default it issues eth_accounts and assumes the wallet is already connected; passing { requestAccounts: true } switches to eth_requestAccounts, which will trigger a connection prompt in the user's wallet UI if no account is connected yet. Prefer gating that on an explicit user gesture (e.g. a "Connect wallet" button) — or pass { account } to skip account discovery entirely.

import {
  createX402bClient,
  signerFromEip1193,
} from "@bosonprotocol/x402-client-browser";

const signer = signerFromEip1193(window.ethereum!, { requestAccounts: true });

const client = createX402bClient({
  signer,
  // ...same config as above
});

End-to-end with wrapFetchWithPayment

Once you have a client, pair it with wrapFetchWithPayment from @bosonprotocol/x402-client-fetch so a request that gets a 402 carrying scheme: "escrow" is transparently retried with the X-PAYMENT header:

pnpm add @bosonprotocol/x402-client-fetch
import { wrapFetchWithPayment } from "@bosonprotocol/x402-client-fetch";

const fetchWithPayment = wrapFetchWithPayment(fetch, client);
const res = await fetchWithPayment("https://seller.example/resource");

License

Apache-2.0