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

@brett_lamy/rion

v0.1.2

Published

Record your Rust/C/C++/Go program under rr and time-travel through every line in the rr-dash dashboard — created by replay.io

Readme

rion

Record your Rust / C / C++ / Go program under rr and time-travel through every line it executed — hit counts, call stacks, watch values at every step, a flamechart, and a scrubbable timeline that streams in live while the recording is still running.

Created by replay.io — the time-travel debugging industry leaders.

npx @brett_lamy/rion record -- ./your-program

Your default browser pops open on the live trace the moment recording starts.

Requirements

  • Docker — recording runs inside a sandboxed rr container (rion builds the image on first use: npx @brett_lamy/rion doctor --build)
  • Node 18+
  • A program built with debug info (-g -O0, cargo dev profile, or go build -gcflags='all=-N -l') — the binary must be a Linux build, since it runs inside the container

Getting started

# 1. Sign in (opens your browser to approve this CLI):
npx @brett_lamy/rion login

# 2. Check your setup (and build the recorder image on first run):
npx @brett_lamy/rion doctor --build

# 3. Record, from your project directory:
npx @brett_lamy/rion record -- ./target/debug/your-program

The trace uploads to rr-dash under your account and starts streaming immediately — you can watch execution arrive line by line while the program is still being recorded.

Commands

| Command | What it does | | --- | --- | | rion login [--server <url>] | Browser-approval sign-in; token cached at ~/.config/rion/auth.json | | rion logout | Forget the saved token | | rion doctor [--build] | Verify Docker, the recorder images, and connectivity | | rion record [opts] -- <cmd…> | Record <cmd> under rr and upload the trace |

record options

| Flag | Default | Description | | --- | --- | --- | | --lang rust\|c\|cpp\|go | auto-detected | Source language | | --src <dir> | cwd | Project directory (mounted into the sandbox) | | --title <string> | the command | Trace title in the dashboard | | --id <recordingId> | generated | Explicit recording id | | --server <url> | rr-dash prod | Dashboard host |

Environment variables

| Variable | Purpose | | --- | --- | | RION_API_KEY | Non-interactive auth (create one at /welcome) — the CI equivalent of rion login | | RION_HOST | Override the default dashboard host | | RION_NO_OPEN | Set to 1 to skip auto-opening the trace in a browser |

How it works

rion record runs your command under rr record (software-counters mode) in a Docker sandbox, replays the trace under gdb to extract per-line hit counts, an ordered linetrace, and sampled call stacks + locals at every step, then uploads everything through the dashboard's authenticated API. Nothing is uploaded anonymously; recordings are attributed to your account.

Prefer zero local setup? The Playground compiles and records small programs in a cloud sandbox instead.