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

@m4trix/trace-viewer

v0.10.0

Published

Filesystem-backed trace viewer CLI with tRPC API and React UI

Readme

@m4trix/trace-viewer

Filesystem-backed trace viewer for @m4trix/tracing: a small HTTP server with a tRPC API (/trpc) and a Vite + React + Tailwind UI.

CLI

From the repo root (after pnpm install, which links this package’s bin):

pnpm exec m4trix-trace-viewer --adapter fs --path ./tmp/tracing-example --port 4319

If pnpm exec still can’t find the command, run it via the workspace filter:

pnpm --filter @m4trix/trace-viewer exec m4trix-trace-viewer --adapter fs --path ./tmp/tracing-example --port 4319
  • --adapter fs — read traces via FsStructureStoreAdapter / FsPayloadStoreAdapter at --path.
  • --adapter aws-stack — prints a clear “not implemented” message and exits.
  • --port — HTTP listen port (default 4319).
  • --path — trace root for fs (default tmp/tracing-example).

Then open http://127.0.0.1:4319 in a browser.

Programmatic usage

import { createFsTraceViewerApi, startTraceViewerServer } from '@m4trix/trace-viewer';

const traceViewerApi = createFsTraceViewerApi('./tmp/tracing-example');
startTraceViewerServer({ traceViewerApi, port: 4319 });

tRPC procedures

  • traces.listTraceViewerApi.listTraces
  • traces.getTreeTraceViewerApi.getTraceTree
  • traces.getPayloadTraceViewerApi.getPayload (lazy load in the UI)

Develop

The package build is intentionally split but still portable:

  • tsup builds the publishable Node library and CLI into dist/.
  • vite build builds the browser app from src/app/index.html into dist/client/.
  • pnpm run build is just tsup && vite build, using package-local binaries resolved by the package manager.
pnpm --filter @m4trix/trace-viewer build
pnpm --filter @m4trix/trace-viewer test