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

@fougere/observability

v0.6.0-alpha.0

Published

Optional observability for Fougere: one span per operation, W3C Trace Context across any transport.

Downloads

303

Readme

@fougere/observability

One span per operation, and the four signals derived from it Optional in the strong sense: core holds no tracing code at all, only a trace field on the invocation that it carries and never reads. An app that does not install this pays nothing.

extensions: [observability({ service: 'blog', otlp: 'http://localhost:4318' })],

The parent rides the invocation, not a header — so the trace crosses whatever the topology became, and the difference between the two spans of a split call is what the wire cost. Rate, errors and duration are one metric (a histogram of durations, dimensioned by the op and by its verdict); saturation is counted by the middleware. OTLP over HTTP in the JSON encoding — no protobuf, no dependency.

rpc.topology is declared here, not by core: an app that never installed this refuses the op by name, which is the whole degradation a reader needs.

Installation

pnpm add @fougere/observability

Part of Fougere — one schema, a gradient from monolith to distributed, the same user code. Reference documentation: the site (en/fr).