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

@streamoid/errors

v0.1.0

Published

Public error messages and recovery metadata for Streamoid applications

Readme

@streamoid/errors

Zero-dependency, browser-safe public error normalization. This package never retries a request. Apps supply operation context and decide which supported recovery action to render.

import { responseError, UserFacingError, isCancellation } from '@streamoid/errors';
let response;
try { response = await fetch(url, options); }
catch (cause) {
  if (isCancellation(cause)) throw cause;
  throw new UserFacingError(cause, { method: options.method });
}
if (!response.ok) throw await responseError(response, { method: options.method });

Existing envelopes remain valid. Services may add publicError: { version: 1, code, message, recovery, operation, safeToRetry, reference }. Only this deliberately public envelope can supply bespoke text; raw exception messages, HTML and provider responses are diagnostic-only. Field validation paths are retained without echoing submitted values. Keep the original cause in protected diagnostics.

Use normalizeError(error) for persistent UI and errorMessage(error) for existing string interfaces (includes a support reference). Pass the request method when known. A missing method is treated conservatively as an unknown write, rather than assuming a read. Never infer retry safety from a 5xx status. Writes with unknown outcomes retain safe authored context and append guidance to check status; only a durable failed/not-started state plus explicit retry safety permits repeat submission. fieldErrors paths must be mapped to visible form labels. Pass intentional cancellation through unchanged and do not display it.

Run npm test --workspace @streamoid/errors. Publish through the repository's reviewed package release workflow, then update consumers; never commit local file dependencies.