provider-utils

This library was generated with Nx.

Building

Run nx build provider-utils to build the library.

Running unit tests

Run nx test provider-utils to execute the unit tests via Jest.

WalletConnect

Use a non-empty Reown project ID whose dashboard allowlist contains the exact application origin. The Pockie deeplink flow must use the display_uri emitted by the same provider that owns the pending connection; do not create a second client only to generate a URI.

Review THIRD_PARTY_NOTICES.md before publishing this package. Reown license acceptance and any applicable commercial-license requirement remain release gates.

The package requires Node.js 18.20.8 or newer, matching the WalletConnect core runtime requirement. showQrModal is retained only as an upstream-deprecated compatibility bridge. New custom UIs should set it to false and render the exact display_uri exposed by the wallet/react-wallet packages. The option remains optional for source compatibility; omitting it keeps the upstream default of not opening the built-in modal.

Public provider and option types use the SDK's stable EIP-1193-compatible surface. This prevents WalletConnect, Coinbase, MetaMask, ethers, and Node type changes from becoming accidental compile-time breaking changes for consumers; the current runtime packages remain the source of implementation behavior. EthereumInpageProvider additionally preserves the complete public member set that the SDK previously exposed through MetaMaskInpageProvider, including legacy send/sendAsync, chainId, selectedAddress, networkVersion, event emitter methods, and _metamask. Non-MetaMask providers use the separately exported minimal EIP1193Provider boundary so WalletConnect's numeric chain ID and Coinbase's current provider shape do not get mixed with MetaMask types.

Coinbase integration uses @coinbase/wallet-sdk v4's createCoinbaseWalletSDK() factory. Existing defaultRpc and defaultChainId configuration remains source-compatible; defaultRpc is deprecated because the v4 SDK discovers RPC endpoints itself. Use optional appChainIds, appLogoUrl, and preference for the current API.

Consumer security pins

WalletConnect currently publishes exact transitive AppKit versions, so the application workspace must keep the following root-level pnpm overrides until the upstream dependency constraints include these patched releases. Dependency package overrides are not inherited by npm or pnpm consumers.

{
  "pnpm": {
    "overrides": {
      "@reown/appkit": "1.8.23",
      "@walletconnect/jsonrpc-ws-connection>ws": "7.5.13",
      "axios": "1.19.0",
      "braces": "3.0.3",
      "picomatch": "2.3.2"
    }
  }
}

Do not replace the scoped ws override with a global ws override because other dependencies may require the incompatible v8 API. Regenerate and commit the application lockfile after adding these pins.