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

failway

v2.0.2

Published

A typescript library for Railway Oriented Programming.

Downloads

24

Readme

Failway GitHub license npm npm bundle size

Failway is a typescript library for elegant error handling.

It's inspired by the concept of Railway Oriented Programming (ROP).

npm i failway

Why ROP?

The worst parts of the code are the parts which handle errors.

Consider the following code from a single page app:

const request = buildRequest();

let response;
try {
    response = await fetchData(request);
} catch (networkError) {
    showNetworkDisconnectedPopup();
    return;
}

if (response.statusCode === 404) {
    display404Page();
    return;    
} else if (response.statusCode === 401) {
    displayLogin();
    return;
} else if (response.statusCode != 200 ) {
    displayErrorPage();
    return;
}

let responseData;
try {
    responseData = parseData(response);
} catch (parseDataError) {
    displayErrorPage();
    return;
}

// Do something with the response data

Ugly, right?

The error handling obstructs the true purpose of the procedure - a call to an API.

With ROP we would write it like this:

const result = Rail(requestInfo)
    .map(buildRequest)
    .map(fetchData)
    .map(checkResponseCode)
    .map(parseData)
    .done()

if (result.status === "OK") {
    // do something with response data
    return;
} else if (result.status === "NETWORK_ERR") {
    showNetworkDisconnectedPopup();
} else if (result.status === "404") {
    display404Page();
} else if (result.status === "401") {
    displayLogin();
} else {
    displayErrorPage();
}

Much cleaner.

ROP allows us to separate the "happy path" from the error handling, thus simplifying the code.

Isn't that just the Promise API?

It looks similar (by design), but it provides a few improvements:

  • Promises are infectious. When a function returns a promise, all callers of the function must make use of the Promise API to access the returned data. The use of promises in the library is optional, so you can compose pipes together without fear of infection.
  • Exceptions in Javascript are terrifying. Any value can be thrown, and there is no static type checking of exceptions. This makes it impossible to handle exceptions in a consistent and safe way. This library accumulates error types into result.err as a union type, so the compiler will check that you handled all of the cases.

Also check out: