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

@notdaniel/tracetana

v0.4.0

Published

Trace your application's journey with the flexibility it deserves. Fork when operations split. Stage as they progress. Discover a user ID three steps in? Apply it retroactively to everything that came before. Build immutable trace contexts that adapt to h

Readme

tracetana

Trace your application's journey with the flexibility it deserves. Fork when operations split. Stage as they progress. Discover a user ID three steps in? Apply it retroactively to everything that came before. Build immutable trace contexts that adapt to how your code actually runs—not how you wish it did.

This is probably not the ideal way to do any of these things, but it's something that worked for me for a specifc use-case.

Installation

npm install @notdaniel/tracetana

Compatibility: Works with both CommonJS and ESM projects. Node.js >= 16.0.0 required.

Quick Start

// Works in both CommonJS and ESM projects
import { Tracer, Publisher } from "@notdaniel/tracetana";
// Or: const { Tracer, Publisher } = require("@notdaniel/tracetana");
import Redis from "ioredis";

const publisher = new Publisher({ redis: new Redis() });

let trace = new Tracer()
  .setPublisher(publisher)
  .stage("request.start", { path: "/api/users" });

await trace.publish();

// Add context discovered later - applies retroactively to all stages
const userId = await authenticate();
trace = trace.withGlobal({ userId });

trace = trace.stage("db.query", { table: "users" });
await trace.publish();

// Fork to track parallel operations
const cacheCheck = trace.fork("cache.lookup");
await cacheCheck.publish();

console.log(`Duration: ${trace.totalDuration}ms`);

Features

  • Immutable contexts - Functional API with no mutation, safe to pass around
  • Retroactive metadata - Use .withGlobal() to add context that applies to all past and future stages
  • Fork for parallelism - Track concurrent operations while maintaining correlation
  • Stage-based flow - Build traces incrementally with .stage() as operations progress
  • Time series analysis - Built-in duration tracking and percentile stats
  • Redis-backed - Streams, hashes, indexes, and stats with configurable TTLs
  • Latency monitoring - Track publisher performance with .getLatencyStats()

Documentation

Requirements

Node.js ≥22.0.0 (ESM only)

License

MIT