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

@saas-pro-lib/payments

v0.1.0

Published

Headless React client, hooks, and small UI helpers for saas-pro-lib payments.

Downloads

12

Readme

@saas-pro-lib/payments

React client, hooks, and small UI helpers for SaaS billing screens.

The package is intentionally split from product policy:

  • this package handles API calls, loading/error state, plan cards, billing-cycle toggles, and Customer Portal buttons
  • each SaaS still owns plan copy, authorization, feature gates, tenant rules, and where the page lives

Expected backend endpoints

By default PaymentsClient calls these paths under apiBaseURL:

| Method | Path | Purpose | | --- | --- | --- | | GET | /v1/payments/plans | list plans | | GET | /v1/payments/subscription | current team subscription | | POST | /v1/payments/checkout | create Stripe Checkout session | | POST | /v1/payments/portal | create Stripe Customer Portal session | | POST | /v1/payments/bank-transfer | create JP bank-transfer subscription | | POST | /v1/payments/change-plan | change plan directly | | POST | /v1/payments/cancel | cancel at period end | | POST | /v1/payments/reactivate | clear pending cancellation | | POST | /v1/payments/cancel-scheduled-change | clear a scheduled plan change |

Override paths with endpoints when a product already has different route names. The Go payments SDK exposes these defaults via mod.HTTPHandler(...).

Usage

import { useState } from "react";
import {
  BillingCycleToggle,
  PaymentsProvider,
  PlanGrid,
  useCheckout,
  usePlans,
  useSubscription,
  type BillingCycle,
  type PaymentPlan,
} from "@saas-pro-lib/payments";

function BillingPage() {
  return (
    <PaymentsProvider apiBaseURL="https://api.example.com">
      <Plans />
    </PaymentsProvider>
  );
}

function Plans() {
  const [cycle, setCycle] = useState<BillingCycle>("monthly");
  const { plans } = usePlans();
  const { subscription } = useSubscription();
  const { startCheckout } = useCheckout();

  const onSelectPlan = async (plan: PaymentPlan) => {
    const url = await startCheckout({ planSlug: plan.slug, cycle });
    window.location.assign(url);
  };

  return (
    <>
      <BillingCycleToggle value={cycle} onChange={setCycle} />
      <PlanGrid
        plans={plans}
        cycle={cycle}
        currentPlanSlug={subscription?.planSlug}
        highlightedPlanSlug="professional"
        onSelectPlan={onSelectPlan}
      />
    </>
  );
}

If your app uses @saas-pro-lib/auth, pass its client as client so auth headers and refresh behavior stay centralized:

<PaymentsProvider apiBaseURL={apiBaseURL} client={proAuthClient}>
  {children}
</PaymentsProvider>