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

@dxo/dxo

v0.0.13

Published

DXO TypeScript CLI (developer preview, API unstable)

Readme

@dxo/dxo

The DXO command-line entry point for Node.js projects.

Developer preview. The CLI is private and its API is unstable. Only commands implemented in the installed build are executable.

Install and invoke

pnpm exec dxo --help
pnpm exec dxo version

For a published release:

pnpm add -D @dxo/dxo
pnpm exec dxo doctor

The CLI does not install a runtime, download model code, or select a remote provider implicitly.

Commands

version

Prints CLI, @dxo/core, and native runtime version information.

dxo version
dxo --version

doctor

Checks Node, native addon loading, backend capabilities, ABI compatibility, and relevant paths.

dxo doctor
dxo doctor --json > doctor.json

--json writes one machine-readable document to stdout; diagnostics go to stderr.

studio

Starts the local Studio inspect API and, unless disabled, the VMZ development UI. It listens on loopback by default.

dxo studio
dxo studio --port 4310 --webui-port 5173 --runs-dir ./.dxo/runs
dxo studio --api-only

--runs-dir selects the append-only run store. The process shuts down cleanly on SIGINT or SIGTERM.

Planned v0 commands

These commands are part of the CLI contract but may not yet be present in the current preview build:

dxo run <entry>                       Execute an explicit TS/JS entry
dxo inspect list                      List local runs
dxo inspect show <run-id>             Show run metadata and event summary
dxo graph <entry>                     Export a DXO model graph or trace
dxo model verify <source>             Verify manifest, digest, and state compatibility

An unavailable command must fail with exit code 2. serve, remote providers, quantization, and multi-GPU commands are outside the current preview surface. When serve lands, it must call a napi-backed runtime — the CLI must not ship a parallel TypeScript HTTP server.

Common options

| Option | Meaning | |-------------------|---------------------------------------------------| | --help, -h | Show help for the current command | | --version, -v | Print version information | | --cwd <path> | Use an explicit project directory | | --config <path> | Load an explicit config file | | --json | Emit one JSON result on stdout; logs go to stderr | | --quiet | Suppress informational output | | --verbose | Include diagnostic logging and stack details | | --no-color | Disable ANSI color output |

Configuration is read from the current directory unless --cwd or --config is supplied. The CLI does not walk parent directories.

Exit codes

| Code | Meaning | |-------|-------------------------------------------------------------------| | 0 | Success | | 1 | User entry, runtime, or model verification failure | | 2 | Invalid arguments, configuration, unknown, or unsupported command | | 78 | Required environment or capability is unavailable | | 130 | Cancelled by SIGINT |

Errors have a stable code, human-readable message, and optional structured details. Stack traces are never written to stdout; use --verbose when diagnosing locally.

Scope and security

The CLI is an orchestrator. Tensor execution belongs to @dxo/core; run protocols to @dxo/inspect; model graphs to @dxo/graph; artifact and state handling to @dxo/hub and @dxo/serialize; the local UI to @dxo/studio.

Network access and remote artifacts are opt-in. Keep tokens and private keys out of config files. The CLI executes Node code with normal user permissions and is not a sandbox.

Development status

The current implementation is intentionally small. Conformance work covers help/version, structured doctor, argument errors, signal cancellation, Studio lifecycle, and JSON output for inspect commands.