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

@swantron/otel-bootstrap

v0.1.2

Published

Drop-in OpenTelemetry bootstrap + synthetic-run-id middleware for white-box watchtron services. Dual CJS + ESM.

Readme

@swantron/otel-bootstrap

Drop-in OpenTelemetry bootstrap for white-box watchtron services. Emits HTTP + Express SERVER spans to the watchtron control plane over OTLP/HTTP JSON, and stamps synthetic run ids onto spans so the control plane can confirm real end-to-end traffic.

Ships dual CJS + ESM because the fleet has both: chomptron is CommonJS, tronswan is ESM.

Install

npm install @swantron/otel-bootstrap

Publishing (automated via CI, no token)

Publishing happens in .github/workflows/ci.yml: on every push to main, after tests pass, the publish-otel-bootstrap job publishes this package to public npm — but only when the version in package.json is not already on the registry (idempotent).

Auth uses npm OIDC Trusted Publishing — short-lived credentials minted per run via GitHub's id-token, so there is no NPM_TOKEN secret to store or rotate. Provenance is attached automatically.

To cut a release: bump version here and merge to main. Consumer repos pin ^0.1.0.

One-time setup (bootstrap)

Trusted publishing is configured per package, so the package must exist first:

  1. Publish v0.1.0 once, locally, with browser auth (no token):
    npm login                       # web-based, no token
    cd packages/otel-bootstrap
    npm publish --access public     # @swantron scope; no org needed
  2. On npmjs.com, open the package → Settings → Trusted Publisher → add a GitHub Actions publisher: repository swantron/watchtron, workflow ci.yml.

After that, all future version bumps publish automatically via CI with zero secrets.

Activation is env-gated

Nothing happens unless WATCHTRON_OTLP_ENDPOINT is set, so local dev and tests are unaffected. Required runtime env on the deployed service:

| Env | Value | | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | WATCHTRON_OTLP_ENDPOINT | https://watch.swantron.com | | WATCHTRON_TOKEN | the control-plane bearer token | | WATCHTRON_SERVICE_NAME | must equal the registry expectedServiceName | | WATCHTRON_SERVICE_VERSION | (optional) the deploy's git SHA — stamped as service.version so verify can assert the new build is actually serving. Defaults to 0.0.0 (version check skipped). |

ESM service (tronswan)

Start the SDK before the app loads via --import:

// package.json
"start": "node --import @swantron/otel-bootstrap/register server.js"

Then add the synthetic-marker middleware early in the Express chain:

import { syntheticMarkerMiddleware } from '@swantron/otel-bootstrap';
app.use(syntheticMarkerMiddleware());

CommonJS service (chomptron)

Require the bootstrap as the very first line of server.js (before express is required) so instrumentation can patch modules:

require('@swantron/otel-bootstrap/register');
const express = require('express');
const { syntheticMarkerMiddleware } = require('@swantron/otel-bootstrap');
// ...
app.use(syntheticMarkerMiddleware());