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

@meterbox/node

v0.1.3

Published

Typed Node.js client for the Meterbox /v1 API, generated from the platform's OpenAPI spec. Shared by the React component SDK and tenant backends.

Readme

@meterbox/node

Typed Node.js client for the Meterbox /v1 API. Generated from the platform's OpenAPI spec via @hey-api/openapi-ts: every public /v1 endpoint is a typed function with full request/response types (TypeScript declarations included).

Used by @meterbox/react for embeddable components; also fine to use directly in your backend.

Install

npm install @meterbox/node

Use

const { MeterboxClient, getV1Plans, postV1CustomersByIdCredits } = require("@meterbox/node");

new MeterboxClient({
  apiKey: process.env.METERBOX_API_KEY, // mb_live_... from Settings > API keys
  // baseUrl: "https://meterbox.ai", the default
});

const { data: plansResponse } = await getV1Plans();
const { data: grant } = await postV1CustomersByIdCredits({
  path: { id: "cus_42" },
  body: { amount_usd: 25, type: "promotional" },
});

API keys are scoped to one environment (sandbox or production), so the key you pass picks the environment.

apiKey is sent as Authorization: Bearer <key>. On a self-hosted deployment you can pass the operator key as adminKey instead (sent as X-Admin-Key).

MeterboxClient configures the generated client singleton, so every operation imported from @meterbox/node picks up that config. To talk to more than one Meterbox deployment from one process, pass client: per operation (each operation accepts one as an override).

Requires Node.js 18 or later.

Regenerate (maintainers)

From a checkout of the Meterbox monorepo:

cd sdks/node
npm run generate

The script dumps the current spec, runs @hey-api/openapi-ts against it, and compiles CommonJS + .d.ts into dist/, which is what ships. Regenerate whenever the API surface changes and commit the dist/ diff.