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

@blossm/errors

v0.0.41

Published

A library of errors that can be thrown by the network.

Readme

A library of errors that can be thrown by the network.

The info passed to this package's error constructors is application-defined public metadata. error.toJSON() and the error middleware preserve its object or array unchanged, together with the explicit error message, code and status. This includes trace/resource IDs, conflict arrays, validation errors and authentication redirects. The middleware also logs status, code, the public message and this declared public metadata for audit correlation. Native error types and stack call sites are retained only in server logs; the complete native message prefix is excluded even when multiline. RPC logs retain operation identity, region and network without raw URLs, forwarded context, credentials or request/response bodies.

Authors must keep public messages and info free of credentials and submitted secrets. RPC must not attach bearer tokens, forwarded request context or raw request payloads to public error metadata. Public info is an explicit contract, not a container for private diagnostics.

error.cause() remains available internally but is never serialized. SDK info() still exposes internal diagnostics, including inherited cause info; those inherited fields are not implicitly published. Errors constructed outside this package are undeclared. Native error stacks, causes, arbitrary toJSON methods and diagnostic info properties are not public response fields. Undeclared native server errors use a generic public message. Middleware does not log raw errors, native messages, causes, or request bodies, queries or parameters.