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

erresult

v1.3.3

Published

This library aims to provide Rust like error handling in typescript.

Downloads

8

Readme

Erresult

This library aims to provide Rust like error handling in typescript.

Error handling

In many languages errors are Values, in rust this is implemented using the Result enum, sadly typescript doesn't provide enums that are powerful enough.

Here is a real code example:

Rust

fn main() {
    let number_str = "42";

    // convert the string to a number (i32 is a number)
    match number_str.parse::<i32>() {
        // Valid case
        Ok(num) => println!("Parsed number: {}", num),
        // Error case
        Err(err) => eprintln!("Error: {}", err),
    }
}

JavaScript

In JavaScript you surely know the try catch control flow, but it has multiple flaws:

  • It doesn't force you to address potential errors
  • It doesn't even provide you with the info that an error could be thrown
  • It creates a new scope
  • As [anything can be thrown](https://kentcdodds.com/blog/get-a-catch-block-error-message-with-typescr ipt) in JavaScript the cached error may not be an error at all
    • There is basically no Type safety

Using Erresult error management looks more like this:

import { result } from "erresult";

const numberStr = "42";

enum Error {
	NotANumber,
	TooBig,
	TooSmall,
}

result<number, Error>((Ok, Err) => {
	const number = parseInt(numberStr);

	if (isNaN(number)) return Err(Error.NotANumber)
	if (number > 1_000_000) return Err(Error.TooBig)
	if (number < 0) return Err(Error.TooSmall)

	return Ok(number)
}).match(
	(value) => console.log(`The parsed number is ${value}`),
	(err) => console.error(`The function returned an error: ${err}`),
	(msg) => console.log(`A error was thrown: ${msg}`)
)

See example.ts for the example above

Documentation

Documentation is available here.