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

@ohm_studio/cli

v0.1.0

Published

OHM Studio CLI — pull your published Studio API schemas and emit typed TypeScript interfaces. Pairs with @ohm_studio/sdk for end-to-end type safety.

Downloads

139

Readme

@ohm_studio/cli

Codegen tool for OHM Studio. Pull your published Studio API schemas and emit typed TypeScript interfaces — pair with @ohm_studio/sdk for end-to-end type safety.

Install

npm i -D @ohm_studio/cli
# or globally
npm i -g @ohm_studio/cli

Quick start

export OHM_API_KEY=ohms_live_xxx

# One API
ohm-studio pull opd-clinic
# → ./ohm-types/opd-clinic.ts

# All published APIs
ohm-studio pull-all --out src/ohm

# What's published?
ohm-studio list

Use the generated types

import { OHM } from "@ohm_studio/sdk";
import type { OpdClinicData } from "./ohm-types/opd-clinic";

const ohm = new OHM({ apiKey: process.env.OHM_API_KEY! });

const { data } = await ohm.extract<OpdClinicData>({
  apiSlug: "opd-clinic",
  text: transcript,
});

// `data` is typed against the schema you defined in Studio
data.diagnoses.forEach((d) => console.log(d.name, d.code));

Pre-build hook

Add codegen to your package.json so types stay in sync with Studio:

{
  "scripts": {
    "predev": "ohm-studio pull-all --out src/ohm",
    "prebuild": "ohm-studio pull-all --out src/ohm"
  }
}

Programmatic API

import { pull, generateTypes } from "@ohm_studio/cli";

await pull({
  slug: "opd-clinic",
  apiKey: process.env.OHM_API_KEY!,
  baseUrl: "https://api.ohm.doctor",
  outDir: "./generated",
});

Auth

The CLI accepts:

  • API keys (ohms_live_*, ohms_test_*) — project-scoped
  • Studio user JWTs — organization-wide

Pass either via OHM_API_KEY env var or --key <token>.

License

MIT