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

@spinajs/telemetry-common

v2.0.522

Published

Metric abstraction shared by @spinajs/telemetry and any package that must publish metrics without depending on the HTTP stack

Readme

@spinajs/telemetry-common

The metric abstraction shared by @spinajs/telemetry and by packages that must publish metrics without taking on the HTTP stack.

@spinajs/telemetry depends on @spinajs/http, @spinajs/log, @spinajs/validation and @spinajs/configuration — it serves /metrics, /health and the telemetry JSON api. A package that only wants to record a metric, such as @spinajs/orm publishing connection-pool gauges, must not drag any of that underneath itself.

So this package holds exactly the part that needs nothing but @spinajs/di and prom-client:

  • Metrics — a @Singleton() wrapper over a PRIVATE prom-client Registry, with the declarative defineMetrics( prefix, defs ) factory and an async Prometheus text renderer,
  • MetricDef / MetricType / AnyMetric / MetricMap,
  • the prom-client metric types, re-exported so consumers need no direct prom-client dependency.

@spinajs/telemetry re-exports all of it, so import { Metrics } from '@spinajs/telemetry' keeps working and both packages share ONE Metrics class identity — which matters, because DI resolves the singleton by that identity and a second copy would mean a second, separate registry.

Same pattern as @spinajs/configuration-common and @spinajs/log-common.