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

no-null

v2.4.0

Published

Rustlike option- and result-types for better null- and error-handling.

Downloads

21

Readme

no-null

Rust-like Result and Option types for safer null-value and error handling.

Examples

Result

The Result-type represents an operation that could fail.

import { Result } from 'no-null';

// Defining a custom result type so we only have to declare the 
// expected ok-result type in our function 
type MyResult<T> = Result<T, Error> // |
                                    // V    
function failWithError(): MyResult<string> {
    try {
        throw new Error("uh-oh");
        // Result.ok() represents a successful operation
        return Result.ok("Success")
    } catch (ex) {
        // Result.err() is a failed operation
        return Result.err(ex as Error)
    }
}

const result = failWithError();

// Matching on Result.ok() and Result.err()
const innerOrDefault = result.match({
    onOk: (someString) => {
        // We can return the inner value or ...
        return someString;
    },
    onErr: (err) => {
        // ... we can return a default value in case
        // result was an err-result
        return "default value";
    }
});

console.log(innerOrDefault);

// Matching only against Result.ok()
// This can not return a value, because it 
// could also be an error
result.ifOk((someString) => {
    // ...
});

// Matching only against Result.err()
result.ifErr((err) => {
    // ...
});

if (result.isOk) {
    // ...
}
if (result.isErr) {
    // ...
}

We could also use error messages instead of an actual error

// Custom result type with error messages
type MsgResult<T> = Result<T, string>;

// This is useful if we want to display an message to an user
function fetchPrice(): MyResult<number> {
    try {
        // Fetching price could fail
        const price: number = api.fetchPrice();
        return Result.ok(price)
    } catch (ex) {
        return Result.err("No connection to server.")
    }
}

fetchPrice().match({
    onOk: (price) => {
        // Update price in UI if successful
        showPriceToUser(price);
    },
    onErr: (errMsg) => {
        // Tell user what went wrong if failed
        showErrorMsgToUser(errMsg);
    }
})

We could even go a step further and return a key to a translation file.

function fetchPrice(): MyResult<number> {
    try {
        // ...
    } catch (ex) {
        return Result.err("network.noConnectionError")
    }
}

fetchPrice().match({
    onOk: (price) => {
        showPriceToUser(price);
    },
    onErr: (errMsgKey) => {
        // Show translated error message to user
        showErrorMsgToUser(
            getTranslation(errMsgKey)
        );
    }
})

Option

The Option-type represents a value that could be null or undefined.

import { Option } from 'no-null';

function couldGetString(): Option<string> {
    const someCondition = // true/false
    return someCondition ? Option.some("Some string") : Option.none();
}

const maybeString = couldGetString();

// Matching on Option.some() and Option.none()
const innerOrDefault = maybeString.match({
    onSome: (someString) => {
        // We can return the inner value or ...
        return someString;
    },
    onNone: () => {
        // ... we can return a default value in case the 
        // option was none
        return "default value";
    }
});

console.log(innerOrDefault);

// Matching only against Option.some()
// This can not return a value, because it 
// could also be a none-option
maybeString.ifSome((someString) => {
    // ...
});

// Matching only against Option.none()
maybeString.ifNone(() => {
    // ...
});

if (maybeString.isSome) {
    // ...
}
if (maybeString.isNone) {
    // ...
}