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

@aerem/telemetry

v0.2.0

Published

Aerem's shared OpenTelemetry setup for Node services. The telemetry contract, enforced by code.

Readme

@aerem/telemetry

Aerem's shared OpenTelemetry setup for Node services. The telemetry contract, enforced by code.

Internal to Aerem. Published publicly because the @aerem scope is, and because there is nothing secret in it — every endpoint and credential comes from the environment.

Install

npm i @aerem/telemetry

Use

1. Register first. Before the framework boots:

// bin/server.ts — the very first import
import { startTelemetry } from '@aerem/telemetry'
startTelemetry()

⚠ Ordering matters. The auto-instrumentations patch http, pg and amqplib at require time. Register after those are loaded and the patches land on nothing — traces come back empty, which looks exactly like no traffic.

2. Set the contract in your stack file, not a baked image:

OTEL_SERVICE_NAME=sunstore-core-service
AEREM_PRODUCT=sunstore
AEREM_TEAM=sunstore-backend
AEREM_ENV=prod
OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318

Miss any of the four and telemetry disables itself with a warning naming what is absent. It never throws — a missing variable must not stop a release.

3. Logs:

import { pinoTelemetryOptions } from '@aerem/telemetry'
export default defineConfig({ ...pinoTelemetryOptions })

Adds trace_id/span_id to every line, and redacts credentials — including error.config.headers.Authorization, which is where a failed Axios call carries a live token.

4. Jobs across a queue:

import { injectTraceHeaders, extractTraceHeaders, jobSpan } from '@aerem/telemetry'

// publishing
channel.sendToQueue(queue, payload, { headers: injectTraceHeaders() })

// consuming
await jobSpan(
  extractTraceHeaders(msg.properties.headers),
  { job: name, queue, messageId: msg.properties.messageId },
  () => runJob(data),
  (err) => (deliveries > maxRetries ? 'dead_lettered' : 'retried'),
)

Auto-instrumentation does not propagate across a broker. This is what puts a failed job under the request that queued it.

5. Health:

import { runChecks, readinessStatusCode } from '@aerem/telemetry'

const report = await runChecks({ postgres, redis, rabbitmq, migrations })
return response.status(readinessStatusCode(report)).json(report)

/health/live checks nothing external — if it checked the database, one blip would restart every replica at once.

Guarantees

  • Never breaks the app. Missing config disables it, a dead collector is invisible, an internal throw is caught and warned.
  • Never learns where telemetry is stored. It sends to the environment's collector. Changing vendor is a collector deploy, not a release.

Full standard: CONTRACT.md in aerem-observability.