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

@triadjs/otel

v0.2.2

Published

OpenTelemetry tracing integration for Triad routers

Readme

@triadjs/otel

OpenTelemetry instrumentation for Triad routers. Opt-in, router-level, adapter-agnostic.

Install

npm install @triadjs/otel @opentelemetry/api

You also need an OpenTelemetry SDK and exporter of your choice — e.g. @opentelemetry/sdk-node with @opentelemetry/auto-instrumentations-node. See docs/guides/observability.md for the end-to-end walkthrough.

Usage

import { createRouter } from '@triadjs/core';
import { withOtelInstrumentation } from '@triadjs/otel';
import { triadPlugin } from '@triadjs/fastify';

const router = createRouter({ title: 'My API', version: '1.0.0' });
router.add(createPet, getPet, listPets);

withOtelInstrumentation(router, {
  tracerName: 'my-api',
  staticAttributes: { env: 'production' },
  includeUserFromState: (state) =>
    (state as { user?: { id: string } }).user?.id,
});

await app.register(triadPlugin, { router, services });

withOtelInstrumentation mutates the router's endpoints and channels in place, replacing their handlers with span-creating versions. It returns the same router instance for convenient chaining.

Spans produced

| When | Span name | SpanKind | | ---------------------------- | -------------------------------- | -------- | | HTTP endpoint handler | <METHOD> <path> | SERVER | | HTTP beforeHandler hook | <endpoint.name>.beforeHandler | INTERNAL | | Channel onConnect | <channelName>.onConnect | SERVER | | Channel client message | <channelName>.<messageType> | SERVER |

Attributes

Every endpoint span is tagged with:

  • http.method, http.route, http.status_code
  • triad.endpoint.name, triad.context
  • enduser.id (when includeUserFromState returns a value)
  • everything from staticAttributes

Channel spans additionally tag triad.channel.name, triad.channel.message.type, and triad.channel.direction.

What it does NOT do

  • Does not configure an SDK or exporter — bring your own.
  • Does not instrument outgoing HTTP or database calls — use @opentelemetry/auto-instrumentations-node or a driver-specific instrumentation package.
  • Does not produce metrics yet — Phase 14.2 will add @triadjs/metrics.

See docs/guides/observability.md for full integration recipes for Honeycomb, Datadog, Grafana Tempo, Jaeger, Sentry, and AWS X-Ray.