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

@streetjs/diagnostics

v1.0.0

Published

StreetJS structured diagnostics reporter: serializes errors into clean JSON DiagnosticEvents on stderr, strips Node-internal stack frames, and emits a 'diagnostic' event. Zero runtime dependencies.

Readme

@streetjs/diagnostics

The StreetJS structured diagnostics reporter: turns any thrown value into a clean, structured DiagnosticEvent, emits it on a 'diagnostic' event, and writes the JSON line to process.stderr. Zero runtime dependencies, ESM.

This is the standalone home of the reporter that also backs the streetjs framework. The framework re-exports this package, so there is a single source of truth.

Install

npm install @streetjs/diagnostics

Usage

import { diagnosticsReporter } from '@streetjs/diagnostics';

// Ship structured diagnostics to your sink of choice.
diagnosticsReporter.on('diagnostic', (event) => {
  metrics.increment('errors', { class: event.errorClass });
});

try {
  doWork();
} catch (err) {
  diagnosticsReporter.report(err, correlationId);
}

Use the shared diagnosticsReporter singleton, or construct your own new DiagnosticsReporter() (it extends EventEmitter).

The event

report(err, correlationId?) produces a DiagnosticEvent:

interface DiagnosticEvent {
  level: 'error' | 'warn';
  errorClass: string;   // constructor name, "StringError", or "UnknownError"
  message: string;
  stack: string[];      // cleaned frames only
  correlationId?: string;
  ts: string;           // ISO 8601
}
  • Error → errorClass is the constructor name (subclasses preserved), message is err.message, and stack is cleaned.
  • string → errorClass is "StringError", message is the string.
  • anything else → errorClass is "UnknownError", message is String(err).

Stack cleaning

Only real at … frames are kept; blank/noise lines and Node-internal frames (node:internal, node_modules/node) are stripped, so the stack shows your code rather than runtime plumbing.

Example

A complete runnable example lives in src/examples/integration.ts:

npm run example -w packages/diagnostics

License

MIT — see LICENSE.