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

@mmmnt/feat-adapter-stripe

v0.1.6

Published

Stripe service adapter for Feat: the Events API becomes a capture window — unpredicted Stripe activity fails the suite

Readme

@mmmnt/feat-adapter-stripe

Service adapter for Feat that turns a Stripe account's Events API into a capture window: every Stripe event that occurs while a scenario runs becomes a captured record — so an unpredicted charge, refund, subscription change, or any other account activity fails the suite by prediction inversion.

// feat.config.json
"services": {
  "stripe": {
    "adapter": "@mmmnt/feat-adapter-stripe",
    "consistency": "eventual",
    "convergenceTimeout": 5000,
    "options": {
      "apiKeyEnv": "STRIPE_SECRET_KEY",
      "types": ["charge.succeeded", "refund.created"]
    }
  }
}
predict success:
  response 200 CheckoutReceipt { orderId: any string }
  stripe has [ charge.succeeded with Charge { amount: 4900, currency: "usd" } ]

Records are { type: event.type, key: event.id, payload: event.data.object }. Declare the service eventual — Stripe's event feed lags the API calls that cause it. The key comes from an environment variable (never config); point it at test-mode keys. options.types narrows the observable universe; omitted, everything the account emits is in scope. No SDK dependency.

Part of Feature — the .feat execution specification language. Docs: https://github.com/mmmnt/feature/wiki

MIT