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

@pixpilot/credit-package-sizing-calculator-ui

v0.1.0

Published

React UI for @pixpilot/credit-package-sizing-calculator.

Readme

@pixpilot/credit-package-sizing-calculator-ui

The editable admin screen for @pixpilot/credit-package-sizing-calculator.

It owns no financial arithmetic. Every figure comes from calculatePricingSummary, recalculated on the keystroke, so nothing on screen can disagree with the inputs that produced it.

import { CreditPackageSizingCalculator } from '@pixpilot/credit-package-sizing-calculator-ui';

<CreditPackageSizingCalculator defaultValue={ADMIN_CREDIT_FEATURE_SCENARIOS} />;

defaultValue takes features in their loosest form — a name, and whatever estimates the caller happens to have — so an application's existing cost-calculator scenario list can be handed over as it stands. Pass value and onChange to control the table instead; onChange always reports normalised rows with stable ids.

Panels

| Panel | Answers | | ----------------------------- | ------------------------------------------------------------------------ | | Model & pricing assumptions | the token rates, package, margin and buffer everything is priced against | | Recommendation cards | what is on sale, what it earns, what to sell instead | | Feature costs | the per-feature costs the whole model is derived from | | Cost per credit & safe limits | the working: allowed COGS, and the two safe credit limits | | Margins, profit & free tier | profit per credit and per package, and what the free allowance costs | | Package sizes | the same price buying 500, 700 or 1,000 credits, side by side |

Notes

  • Nothing is persisted. The screen is a model to argue with, not configuration the product reads. No production credit cost, Stripe price, or balance is touched.
  • Inputs report only valid figures. The calculator validates its input and throws on anything else, so a cleared box keeps its draft on screen while the calculation behind it keeps the last figure it could use.
  • Margin states are named, not coloured. Healthy, Acceptable, Below target and Not calculable each carry text and an icon.
  • Currency is a prop. Pass format={{ currency, locale }} to price in something other than United States dollars; every panel reads its figures through the same formatters.