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

@usebutr/react

v2.0.1

Published

React provider and hooks for butr. Depends on @usebutr/core, react, zustand.

Readme

@usebutr/react

React provider and hooks for butr. Depends on @usebutr/core, react, zustand.

Part of butr, a multi-chain wallet discovery and connection-state library. Your application owns the picker UI and chain client.

Install

npm install @usebutr/react @usebutr/wallets zustand

React 19+ is a peer dependency. Run this inside an existing React app; the picker UI belongs to your application.

Usage

import { WalletManagerProvider, useConnect, useDiscoveredWallets, useWallet } from "@usebutr/react";
import { autoDiscovery } from "@usebutr/wallets";

// Read once at mount: define it at module scope.
const config = { sources: [autoDiscovery()] };

const WalletPicker = () => {
  const wallets = useDiscoveredWallets();
  const wallet = useWallet();
  const { connect, error, status } = useConnect();

  if (wallet) {
    return <p>{wallet.account.walletAddress}</p>;
  }
  return (
    <>
      {wallets.map(({ id, name }) => (
        <button
          disabled={status === "connecting"}
          key={id}
          onClick={() => connect(id)}
          type="button"
        >
          Connect {name}
        </button>
      ))}
      {error && <p role="alert">{error.message}</p>}
    </>
  );
};

export const App = () => (
  <WalletManagerProvider config={config}>
    <WalletPicker />
  </WalletManagerProvider>
);

WalletManagerProvider creates one manager per mount and starts it in an effect, so nothing runs during a server render. To render persisted connections from the first paint, pass initialState={readWalletSnapshot(cookies)} from a Server Component, with a cookie-backed storage driver on the client.

Hooks

  • Actions: useWalletManager() returns the manager: connect, disconnect, disconnectAll, requestAccounts, setAccount, setActive, setSelection and clearConnectionError are stable references, and getState() reads without subscribing.
  • Connecting: useConnect() returns connect(id), which never rejects (the outcome lands in status and error), connectAsync(id), which resolves the wallet or rejects with a ConnectionError, plus reset, connectingId, status and error.
  • State: useDiscoveredWallets, useConnectedWallets, useWallet(id?), useSelectedWallet(platform), useAccounts(id?), useConnectionStatus, useIsHydrated, useIsReconnecting(id?), and useWalletState(selector) for anything else. Omitting the id reads the active wallet; null reads none.
  • Grouped: useDiscoveredWalletsByPlatform and useConnectedWalletsByPlatform.
  • Async reads: useSigner(wallet) and useBalance(wallet, { account?, token? }) take the entry from useWallet() or useSelectedWallet(platform) and return { data, error, status }, where error is always an Error. They stay "idle" without a wallet and while it is reconnecting, and useBalance stays idle for wallets without getBalance.

Capabilities are checked by presence: render a "sign" button only when wallet.connector.signMessage exists.

Documentation

License

MIT, copyright 2026 Pedro Filho.