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

unthrown

v5.12.2

Published

Explicit errors as values, with a separate defect (panic) channel

Readme

unthrown

Explicit errors as values for TypeScript — with a separate defect channel for the unexpected, and qualification enforced at every boundary.

📖 Documentation · API Reference

pnpm add unthrown

No peer dependencies — the exhaustive error matcher is built-in and exported as match / P.

import { fromPromise, P, TaggedError } from "unthrown";

class NotFound extends TaggedError("NotFound") {} // our modeled domain failure
class NotFoundError extends Error {} // what `fetchUser` rejects with on a 404

const user = fromPromise(fetchUser(id), (cause, defect) =>
  cause instanceof NotFoundError ? new NotFound() : defect(cause),
);

const status = await user.match({
  ok: () => 200,
  // `errCases` takes the exhaustive matcher — every case of E named:
  errCases: (matcher) => matcher.with(P.tag("NotFound"), () => 404),
  defect: () => 500,
});
  • Errors as values via Result<T, E> / AsyncResult<T, E>.
  • A separate defect channel for the unexpected — invisible to the type, observable only via match / recoverDefect and the tapDefect / tapFailure observers.
  • Qualification at every boundary — fromPromise / fromThrowable force you to triage each failure into a modeled error or a defect.
  • Tagged errors — TaggedError(tag) + P.tag(t), folded exhaustively through match's built-in error matcher.
  • Zero runtime dependencies (the matcher is built-in), ESM-first, dual CJS/ESM.

See the full documentation for the guide and complete API.

License

MIT © Benoit TRAVERS