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

@baseworks/pay

v0.1.1

Published

Payments capability: typed HTTP client, event catalog, projections, and CLI plugin for pay-service (idempotent charges against a pluggable provider). Contract-first, versioned with the service.

Readme

@baseworks/pay

Typed client, event catalog, projections, and CLI plugin for pay-service — the per-org payment-collection capability. Contract-first, versioned with the service.

pnpm add @baseworks/pay

Client

Everything is org-scoped (X-Org-Id + identity token). Money is integer cents.

import { createPayClient } from '@baseworks/pay'

const pay = createPayClient({
  baseUrl: process.env.PAY_SERVICE_URL!,
  token:   identityJwt,
  orgId:   activeOrgId,
})

// charge a customer (customerId is a customers-service ref — validated, name
// snapshotted). Idempotent by idempotencyKey: re-sending returns the same payment.
const payment = await pay.charge({
  customerId: 'acct-42',
  amountCents: 5000,             // $50.00
  currency: 'USD',
  provider: 'manual',           // 'manual' | 'mock'
  idempotencyKey: 'invoice-7-attempt-1',
  invoiceId: 'inv_123',         // optional — the invoice this settles
})
// → { status: 'succeeded', providerRef: 'manual:…', … }

await pay.list({ status: 'succeeded' })
await pay.list({ customerId: 'acct-42' })
await pay.get(payment.id)

Errors throw PayError (.status, .code): 400 bad_amount, 404 customer_not_found. A declined charge is not an error — it returns a payment with status: 'failed' and a failureReason.

CLI plugin

import { buildPayCommand } from '@baseworks/pay/cli'

program.addCommand(buildPayCommand({ http, cliName: 'dtab' }))
// dtab payments | pay   ls (--status --customer) · charge · get
//   dtab payments charge --customer <ref> --amount 50.00 --key <id> [--provider mock] [--invoice <ref>] [--fail]

Service integration

import { PROJECTIONS, POLICIES } from '@baseworks/pay/projections'
import { PaymentEvents } from '@baseworks/pay/events'

Projection paymentsread_payments, keyed by the payment stream id (= sha256(payment:<idempotencyKey>)) so a duplicate charge collapses to one row. Tenant = org id.

See also

Service: projects/pay-service · ADR-010.