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

@dainamite/cpq-billing-connector

v0.1.0

Published

Wires @dainamite/cpq subscription lifecycle events to @dainamite/billing API calls (activated / amended / renewed / cancelled / merged / superseded).

Readme

@dainamite/cpq-billing-connector

Pre-built integration that wires @dainamite/cpq subscription lifecycle events to @dainamite/billing API calls.

It depends on both @dainamite/cpq and @dainamite/billing (as peers) and must be registered after both so their services are resolvable when its subscribers fire:

// src/modules.ts — order matters
{ id: 'cpq', from: '@dainamite/cpq' }
{ id: 'billing', from: '@dainamite/billing' }
{ id: 'cpq_billing_connector', from: '@dainamite/cpq-billing-connector' }
yarn generate
yarn mercato db migrate

There is no UI or schema of its own to configure — it is pure event glue. Engines: Node ≥ 24.

The connector subscribes to six CPQ lifecycle events and translates each to the billing API contract:

| CPQ event | Connector action | |---|---| | cpq.subscription.activated | Create Billing Account if missing; create Billing Items per charge (one-time + recurring split) | | cpq.subscription.amended | Create new Billing Items for added subscription items; compute proration value for the partial cycle and post as one_time Billing Item; set bill_end_date on removed items | | cpq.subscription.renewed | Extend bill_end_date on existing Billing Items; create new Items for any added subscription items | | cpq.subscription.cancelled | Set bill_end_date on all Billing Items for the subscription | | cpq.subscription.merged | Move Billing Items from source subscriptions to the merged subscription (update subscription_id) | | cpq.subscription.superseded | Set bill_end_date on all Billing Items for the superseded subscription |

Status

Built — publishing soon (alongside @dainamite/billing; not yet on npm). All six subscribers are wired end-to-end — @dainamite/cpq emits the matching events (cpq.subscription.activated on new-sale activation, the ARC events on amend / renew / cancel / merge). Proration math lives in this package: the amended subscriber derives the bill cycle from the billing account via billing's cycleContaining (CPQ stays neutral on billing-calendar semantics).

See specs/implementation/xd-249-billing-spec.md § CPQ Integration for the full design.

License

MIT