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

@les3dev/catch_error

v1.0.0

Published

A tiny helper that turns thrown errors into values you can branch on

Downloads

105

Readme

catch_error

A tiny helper inspired by Rust's Result type that turns thrown errors into values you can branch on — concise control flow, zero ceremony.

Why use this

  • Avoid try/catch weird control flow
  • Forces to handle errors before accessing returned values
  • Treat errors as values (like Result), so you can use normal control flow to handle them.
  • Works with both synchronous functions and promises (returns a promise when given one).

What it does

The catch_error helper runs a sync function or accepts a Promise and returns either the successful value or an Error instance with a TypeScript union type. Instead of throwing, failures are returned so callers can check instanceof Error and handle errors inline.

See the implementation in catch_error.ts.

API

  • catch_error(fn: () => T): T | Error — runs fn and returns either the value or an Error.
  • catch_error(promise: Promise<T>): Promise<T | Error> — returns a promise that resolves to either the value or an Error.

Errors that are not Error instances are wrapped in a fallback Error with a helpful message.

Examples

Sync example:

import {catch_error} from "./catch_error"; // or from the published package

function parseIntStrict(s: string) {
    if (!/^-?\d+$/.test(s)) throw new Error("not an integer");
    return Number(s);
}

const result = catch_error(() => parseIntStrict("42"));
if (result instanceof Error) {
    // handle error
    console.error("Failed to parse:", result.message);
} else {
    // use value
    console.log("value is", result);
}

Async example:

import {catch_error} from "./catch_error";

const valueOrErr = await catch_error(fetch_data());
if (valueOrErr instanceof Error) {
    // handle error
    console.error("fetch failed", valueOrErr);
} else {
    console.log("data", valueOrErr);
}

Custom error example:

class NotFoundError extends Error {
    constructor(message: string, body: any) {
        super(message);
        this.name = "NotFoundError";
        this.status = 404;
        this.body = body;
    }
}
const result = await catch_error(async () => {
    const res = await fetch("https://les3.dev/not_found");
    if (res.status === 404) {
        throw NotFoundError("page not found", await res.json());
    }
    return await res.json();
});
if (result instanceof NotFoundError) {
    console.log(result.status, result.message, result.body);
} else if (result instanceof Error) {
    console.log("Unknown error: ", result.message);
} else {
    console.log("Success: ", result);
}

See the tests in catch_error.test.ts for more usage examples