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

rez-ts

v1.4.0

Published

So you think error-handling in TypeScript sucks? Congratulations you've found the right lib!

Downloads

1

Readme

Rez TypeScript

So you think error-handling in TypeScript sucks? Congratulations you've found the right lib!

Rez provides an alternative way to handle failures. A way that is:

  • Transparent: Makes all possible failures visible via function signatures.
  • Rigorous: Makes it possible to define and handle errors by type.
  • Enforcing: Makes error-handling a must.
  • Fluent: Makes advanced error-handling easy to reason about.

Installation

Run npm install rez-ts. Then import { define, AsyncResult, Result, exhaust } from "rez-ts";

Usage

Rez allows you to define a fluent result monad that can hold a rigorous set of typed failures that all become transparent within the type system:

public trySaveToDB = <TName extends DBStoreName>(plainRecord: DTO<TName>): AsyncResult<"()", "db: no connection" | "db: non-existing store">;

The first type argument of the AsyncResult, I.e "()" represents the value of the result if the function should succeed. The second type "db: no connection" | "db: non-existing store" represents known failure codes the function can fail with.

Using pattern matching we can easily handle each failure separately with side effects.

await trySaveToDB(record)
    .onSuccess(notifyRecordSaved)
    .onFailure(failure => {
        if (failure.type === "db: no connection")
            handleNoConnection(failure.error);
        else if (failure.type === "db: non-existing store")
            handleNoStore(failure.error);
        else
            exhaust(failure.type);
    });

This way of handling failures is not always ideal. Sometimes we need to design with fault tolerance in mind, we need a way to recover.

 await trySaveToDB(record)
   .tryRecoverFrom("db: no connection")
   .with(putInQueueStorage); 

After a recovery we're free to continue traveling on our happy path result chain.