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

iron-oxide

v1.4.0

Published

Rust style exception handling in TypeScript

Downloads

33

Readme

iron-oxide

Rust style exception handling in TypeScript

Documentation

Documentation is hosted as an mdbook at iron-oxide.js.org.

Option

An Option represents success or the presence of a value. It comes in two variants:

  • None to indicate failure or the lack of a value
  • Some(value) to indicate the presence of the given value

Example:


import { Option, None, Some } from 'iron-oxide';

function find<T>(array: T[], predicate: (el: T) => boolean): Option<T> {
    for (const el of array) {
        if (predicate(el)) {
            return Some(el);
        }
    }

    return None();
}

Result

A Result is like Option, but it also can represent the failure state with a reason. It also comes in two variants:

  • Err(error) to indicate an error state, along with a message of why
  • Ok(value) to indicate the success state

Example:


import { Result, Ok, Err } from 'iron-oxide';

function parseInt(n: string, radix: number = 10): Result<number, string> {
    const value = Number.parseInt(n, radix);

    if (isNaN(value)) {
        return Err(`Unable to parse ${n} as an integer`);
    }

    return Ok(value);
}

Match

A match statement is like a switch statement on steroids. It can be used similarly to switch, but works with more than just primitive values. Namely, you can hand it a primitive value, an object, an array, or a function which returns a boolean.


import { match } from 'iron-oxide';

function isEvenOrOdd(n: number) {
    return match (n, [
        [0, () => 'neitherEvenNorOdd'],
        [x => x % 2 === 0, () => 'even'],
        [x => x % 2 !== 0, () => 'odd']
    ]);
}