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 🙏

© 2024 – Pkg Stats / Ryan Hefner

errly

v0.0.2

Published

Better error handling in TypeScript.

Downloads

6

Readme

Errly

Install size

Error handling in JavaScript is done using try...catch blocks, which can get messy and verbose very quickly. Errly makes the error handling experience similar to that of Golang.

Features

  • Zero dependencies. Small bundle size.
  • Written in TypeScript.
  • Seamless support for synchronous & asynchronous functions.
  • Modern ESModules support.

Usage

Consider the following function:

const throwIfEven = (num: number) => {
    if (!(num % 2)) throw new Error("It's even!");
    return num;
};

Here's how you would normally handle errors from calls to throwIfEven:

function main() {
    try {
        // Happy path:
        const data = throwIfEven(6);
        console.log(data);
        // ...
    } catch (error) {
        // Sad path:
        console.log((error as Error).message);
        return;
    }
}

One issue here is that data is now scoped to the try block, and cannot be used outside of it. Same goes for error being scoped to the catch block. Here's how the same piece of logic looks when using Errly to handle the error:

import { e } from 'errly';

function main() {
    // Scoped to the function.
    const [data, err] = e(() => throwIfEven(6));
    // Write error handling logic first.
    if (err !== null) {
        // Sad path:
        console.log(err.message);
        return;
    }
    // Happy path:

    // TypeScript will understand that "data" is
    // definitely a number and can't be null because
    // the error path was handled above.
    console.log(data);
    // ...
}

With async code

Usage with async functions is the same as above with only the addition of the await keyword.

const doStuff = async () => {
    // Wait for two seconds
    await new Promise((r) => setTimeout(r, 2e3));
    throw new Error('foo');
};

const [_, err] = await e(() => doStuff());
if (err !== null) {
    // Handle error
}

Creating new functions

If using e() all the time doesn't seem like your style, you can instead convert regular functions into Errly functions by using func().

import { func } from 'errly';

const add = func((n1: number, n2: number) => {
    const sum = n1 + n2;
    if (sum > 100) {
        throw new Error('Sum is massive!');
    }

    return sum;
});

const [sum, err] = add(1337, 420);
if (err !== null) {
    // Handle error
}