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

@pushcash/react

v0.1.1

Published

React bindings for the Push UX Web SDK — <PushUX> and <PushWidget> components wrapping window.PushCash.

Readme

@pushcash/react

React bindings for the Push UX Web SDK — a <PushUX> component that presents the Push-hosted payment UX in a modal, and a <PushWidget> component that renders the card-entry form. Both are thin wrappers over the always-latest core loaded from cdn.pushcash.com.

Install

npm install @pushcash/react

react and react-dom (>=17 <20) are peer dependencies you already have. The package injects the core from cdn.pushcash.com at runtime, so allowlist that host in your CSP script-src and frame-src. If the core cannot load (host blocked by CSP, or a network/CDN failure), the modal simply does not appear — verify the CSP during integration.

Usage

Once your submit handler's POST /authorize returns 202 { id }, render <PushUX> with that intent id. It presents the modal on mount and renders nothing itself:

import { PushUX } from '@pushcash/react';

function Checkout({ intentId }: { intentId: string }) {
  // Render this only once you hold an intent id (e.g. after the 202); unmount it to end the flow.
  return <PushUX intentId={intentId} onExit={() => refetchIntentStatus(intentId)} />;
}

<PushUX> owns the lifecycle: it presents the modal when the core is ready, re-presents it if intentId changes, and destroys the handler on unmount — so you never leak an instance.

onExit is advisory: it fires once when the flow ends (completion or dismissal) and carries no result. The authoritative outcome is the server's — fetch it from your backend (GET /intent) or the intent webhook and route the user from there.

Collecting a card with <PushWidget>

<PushWidget> renders the Push card-entry form. Enable your submit button from onValid, then call tokenize() through a ref to get a one-time token for POST /authorize:

import { PushWidget } from '@pushcash/react';
import type { PushWidgetRef } from '@pushcash/react';
import { useRef, useState } from 'react';

function CardForm({ url }: { url: string }) {
  const widget = useRef<PushWidgetRef>(null);
  const [ready, setReady] = useState(false);

  const pay = async () => {
    const result = await widget.current?.tokenize();
    if (!result) return;
    // send result.token to your backend, which calls POST /authorize
    await yourBackend.authorize(result.token);
  };

  return (
    <>
      <PushWidget ref={widget} url={url} onValid={() => setReady(true)} />
      <button onClick={pay} disabled={!ready}>Pay</button>
    </>
  );
}

url comes from the create-user-url endpoint. <PushWidget> renders the form on mount and tears it down on unmount.

License

MIT