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

@apiosk/checkout-react

v0.1.0

Published

React wrapper for the Apiosk four-layer checkout button

Readme

@apiosk/checkout-react

React and Next.js wrapper for the Apiosk four-layer checkout button.

This package does not reimplement the UI logic. It mounts the shared @apiosk/checkout-web custom element and passes the normalized config through to that runtime.

Install

After publish:

npm install @apiosk/checkout-react @apiosk/checkout-web @apiosk/checkout-core

Before publish:

npm install ./subs/checkout-react ./subs/checkout-web ./subs/checkout-core

Quick start

import { PayWithApioskButton } from "@apiosk/checkout-react";

export function MerchantCheckout() {
  return (
    <PayWithApioskButton
      merchantName="Northstar Marketplace"
      productName="Automation bundle"
      amountLabel="24.95 EUR"
      orderReference="ord_2048"
      subtitle="One trigger for humans, agents, and programmable rails."
      rails={[
        {
          id: "credits",
          status: "live",
          launchUrl: "https://gateway.apiosk.com/geocode/forward",
        },
        {
          id: "x402",
          status: "live",
          launchUrl: "https://gateway.apiosk.com/geocode/forward",
        },
        {
          id: "agent",
          status: "pilot",
        },
      ]}
      callbacks={{
        successUrl: "https://merchant.example/success",
        cancelUrl: "https://merchant.example/cancel",
        webhookUrl: "https://merchant.example/webhooks/apiosk",
      }}
    />
  );
}

Ref API

import { useRef } from "react";
import { PayWithApioskButton } from "@apiosk/checkout-react";

const checkoutRef = useRef(null);

<PayWithApioskButton ref={checkoutRef} config={config} />;

checkoutRef.current?.openCheckout();

The component exposes:

  • openCheckout()
  • closeCheckout()
  • element

Why this wrapper exists

The React package should stay thin. The DOM runtime belongs in @apiosk/checkout-web, and the shared schema belongs in @apiosk/checkout-core.

That keeps React, Vue, and plain HTML integrations aligned around one contract.