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

@youneed/server-middleware-trace

v0.1.0

Published

@youneed/server middleware: W3C traceparent distributed tracing (dependency-free, OpenTelemetry-compatible IDs).

Readme

@youneed/server-middleware-trace

W3C Trace Context distributed tracing for @youneed/server. Dependency-free and OpenTelemetry-compatible (16-byte trace id / 8-byte span id, lowercase hex) — without pulling in the OTel SDK. Parses an incoming traceparent, starts a span, propagates a traceparent response header, and hands the finished span to your exporter via onEnd.

import { Application, Response } from "@youneed/server";
import { tracing, span } from "@youneed/server-middleware-trace";

const app = Application()
  .use(tracing({ onEnd: (s) => exporter.push(s) }))   // → traceparent: 00-<traceId>-<spanId>-01
  .get("/users", (ctx) => {
    span(ctx).setAttribute("user.count", 3);
    span(ctx).addEvent("queried-db");
    return Response.json([/* … */]);
  });

The exported framework symbol trace is a request-scoped log line — this middleware is tracing() and the accessor is span() to avoid the clash.

API

  • tracing(opts?) — middleware. For each request: reuses an incoming traceparent's trace id (continuing the upstream trace, its parent-id becoming this span's parent) or starts a fresh trace id; mints a new span id; stores the {@link Span} on ctx.state.span. Options:

    • responseHeader — emit the traceparent response header (default true).
    • onEnd(span) — called in a finally with the finished span (duration recorded). The integration hook: export to OpenTelemetry / Jaeger / Zipkin, log it, etc.

    The span name is set to "<METHOD> <path>" (path without query — low cardinality).

  • span(ctx) — the per-request {@link Span} (a no-op span when the middleware isn't installed):

    • traceId / spanId / parentId? — W3C/OTel ids (lowercase hex).
    • name, startTime, endTime?, duration?.
    • attributes, events — OTel-style bags.
    • setAttribute(key, value) / addEvent(name) — chainable.
    • end() — stamp endTime/duration (idempotent; the middleware calls it).