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

@cashu/coco-react

v2.0.0

Published

React hooks and providers for integrating a Coco `Manager` into React applications.

Downloads

511

Readme

@cashu/coco-react

React hooks and providers for integrating a Coco Manager into React applications.

The package exports the CocoCashuProvider convenience wrapper, which can initialize Coco from config or accept an existing manager, the underlying providers, operation-oriented hooks such as useSendOperation, useReceiveOperation, useMintOperation, and useMeltOperation, plus derived-data hooks such as usePaginatedHistory, useBalances, and useTrustedBalance.

Install

npm install @cashu/coco-react @cashu/coco-core react

react is a peer dependency. The current package peer range targets React 19.

Usage

import { CocoCashuProvider, localStorageSeedGetter, useSendOperation } from '@cashu/coco-react';

const seedGetter = localStorageSeedGetter();

function SendButton() {
  const { prepare, execute, currentOperation, executeResult, isLoading } = useSendOperation();
  const awaitingConfirmation = currentOperation?.state === 'prepared';

  async function handleSend() {
    if (awaitingConfirmation) {
      await execute();
      return;
    }

    await prepare({ mintUrl: 'https://mint.example', amount: 100 });
  }

  return (
    <button disabled={isLoading} onClick={() => void handleSend()}>
      {awaitingConfirmation ? 'Confirm send' : executeResult ? 'Sent' : 'Prepare send'}
    </button>
  );
}

export function App() {
  return (
    <CocoCashuProvider
      config={{ repo, seedGetter }}
      fallback={<div>Loading wallet...</div>}
      errorFallback={<div>Wallet failed to load.</div>}
    >
      <SendButton />
    </CocoCashuProvider>
  );
}

localStorageSeedGetter() stores a generated browser seed under COCO_REACT_SEED by default. Pass localStorageSeedGetter({ storageKey }) to use a different localStorage key. The helper requires the Web Locks API so seed initialization is serialized across same-origin browser contexts. Call it from a secure browser context (HTTPS or localhost), and provide another seedGetter in environments without window.navigator.locks.

If your application already owns the manager lifecycle, pass an initialized manager instead:

<CocoCashuProvider manager={manager}>
  <SendButton />
</CocoCashuProvider>

The config prop is initial-only. Remount the provider with a new React key when you intentionally need to initialize with a different config.

Each operation hook stays bound to one local operation flow for the lifetime of that hook instance. It starts unbound until you call the hook's creation action such as prepare(), and you can also initialize it from an existing operation or operation id for resume screens. That initial hook argument is only used on the first render; if a mounted component needs to switch to a different operation, remount the hook or component with a new React key.

See the docs in packages/docs for provider composition and hook usage details.