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

@rustra/devtools

v0.7.2

Published

Devtools for rustra-bridge — instrumented engine with call stats

Readme

English | 한국어

@rustra/devtools

An observability engine wrapper for rustra invocations. Wraps any EngineClient and records call counts, error counts, and cumulative latency.

Install

bun add @rustra/devtools

createInstrumentedEngine

import { createInstrumentedEngine } from '@rustra/devtools';
import { configure } from '@rustra/types';
import { createNodeEngine } from '@rustra/node';

const engine = createInstrumentedEngine(createNodeEngine({ invoke: myTransport }));
configure(engine);

await addNumbers({ a: 1, b: 2 });
console.table(engine.report().commandStats);
// ┌─────────┬───────┬────────┬─────────┬────────┐
// │ (index) │ count │ errors │ totalMs │ avgMs  │
// ├─────────┼───────┼────────┼─────────┼────────┤
// │ addNum… │ 1     │ 0      │ 3       │ 3      │
// └─────────┴───────┴────────┴─────────┴────────┘

report() returns { totalCalls, commandStats, batchStats, slowest }:

  • commandStats — per-command count/errors/totalMs/avgMs
  • batchStats — batch count/entry count/failure count/total and average latency. It does not guess at a specific command as the cause of a single batch failure.
  • slowest — the 10 slowest calls ({ command, ms })

Behavioral contract

  • Transparent wrapping — instrumentation never removes functionality. The options (signal/timeoutMs) of invoke(command, args, options) are passed to the inner engine as-is, and if the inner engine supports invokeById/invokeBatch, the wrapper forwards them too.
  • Timing — prefers the monotonic high-resolution performance.now(), falling back to Date.now() only in embedded JS runtimes that lack that global.
  • Memory bound — does not retain the full call history; keeps only the 10 slowest calls.

Related docs