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

@opendeviceio/sdk

v0.1.0

Published

TypeScript SDK for OpenDeviceIO (.odio.json): generated types, Ajv 2020 validator, and convenience accessors built against the canonical v0.1 device schema.

Readme

@opendeviceio/sdk

TypeScript SDK for the OpenDeviceIO (.odio.json) format — generated types, an Ajv 2020 validator, and convenience accessors, built against the canonical v0.1 device schema.

The schema is the single source of truth. This package bundles a self-contained copy of schema/v0.1/device.schema.json at build time (src/schema.ts), so the published package never depends on the location of the schema on disk. The TypeScript Device interface in src/types.ts is generated from that same schema with json-schema-to-typescript and committed as source, so consumers get types without running codegen.

Ships as ESM + CJS, fully typed.

Install

npm install @opendeviceio/sdk

Usage

Validate a document

import { validate } from "@opendeviceio/sdk";

const result = validate(JSON.parse(fileContents));
if (!result.valid) {
  for (const e of result.errors) {
    console.error(`${e.path}: ${e.message}`);
  }
}

validate(obj) never throws and returns:

{ valid: boolean; errors: ValidationError[] }
// ValidationError = { path, keyword, message, params }

Parse with typed result (throws on invalid)

import { parse, OdioValidationError } from "@opendeviceio/sdk";

try {
  const device = parse(fileContents); // string or already-parsed object
  console.log(device.device.manufacturer, device.device.model);
} catch (err) {
  if (err instanceof OdioValidationError) {
    console.error(err.message); // readable, multi-line list of failures
  } else {
    throw err; // e.g. SyntaxError for malformed JSON
  }
}

Accessors

All accessors operate on a validated Device and correctly handle the layered model (port.link, port.signals[], signal.transport, signal.channels, port.count — a port with count: 8 represents 8 connectors).

import {
  inputPorts,
  outputPorts,
  portsByConnector,
  allSignals,
  signalsByDomain,
  signalsByTransport,
  totalTypicalWatts,
  totalMaxWatts,
  estimatedBtuPerHour,
  poeBudget,
  rackUnits
} from "@opendeviceio/sdk";

inputPorts(device);                       // direction input | bidirectional
outputPorts(device);                      // direction output | bidirectional
portsByConnector(device, "rj45");         // ports by connector vocabulary value
allSignals(device);                       // [{ port, signal }, ...] flattened
signalsByDomain(device, "audio");         // flows in a domain
signalsByTransport(device, "dante");      // flows by transport
totalTypicalWatts(device);                // power.consumptionWatts.typical
totalMaxWatts(device);                    // power.consumptionWatts.max
estimatedBtuPerHour(device);              // heatBtuPerHour, else maxWatts * 3.412
poeBudget(device);                        // sum of link.poe.classWatts * count, role === "pse"
rackUnits(device);                        // physical.rackUnits

For example, a switch port { count: 8, link: { poe: { role: "pse", classWatts: 30 } } } contributes 8 * 30 = 240 W to poeBudget(device).

Scripts

| Command | Description | | ------------------ | --------------------------------------------------------------------------- | | npm run gen-types| Regenerate src/schema.ts and src/types.ts from the canonical schema. | | npm run build | Run gen-types, then compile ESM + CJS with type declarations into dist/.| | npm test | Run the Vitest suite (conformance corpus + accessor unit tests). | | npm run validate | Validate .odio.json files (defaults to the repo example corpus) via CLI. |

Development

npm install     # inside packages/ts-sdk only
npm run build
npm test