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

resolvjs

v1.0.2

Published

Avoid Towers of Terror and Pyramids of Doom

Downloads

4

Readme

Resolv.js

a small promise handler.

Abstract

This is a small utility to make handling promises a little more readable. Avoiding Towers of Terror and Pyramids of Doom.

Usage:

resolve() takes the promise to resolve as its first argument, optionally takes a boolean for the second parameter; convertToError, finally it optionally takes the parameters of JSON.stringify (save for the first) as the remaining parameters, to be used when stringifying errors.

If convertToError is

  • true, and an error is given that's not an instance of Error, resolve() will return an instance of Error with the given error stringified on the message property.
  • given a falsy value, instances of Object and Error will be returned as-is, while primitives will be treated as if true was provided. This is the default behavior.
  • explicitly false, the error will always be returned as-is. If you wish for this to be the default behavior, import the named export resolve rather than using the default export.

resolve() returns a tuple; [res, err]. Where res is the result of the promise, and err is an error, if one was encountered. The values are mutually exclusive, so if one is defined, the other will be undefined.

JavaScript:

import resolve from "resolvjs"
import anAsyncFunction from "some-api-client"

const [res, err] = await resolve(anAsyncFunction())
if (err) throw err // or handle it in some other way

console.log(res)

TypeScript:

resolve() is a generic function, enabling you to specify the type of the result in such cases where it cannot be or is incorrectly inferred. However, the returned type for res will always be R | undefined, this allows you to use a guard pattern, as shown below, to ensure that errors are always handled. After which, res will be of type R.

import resolve from "resolvjs"
import anAsyncFunction from "some-api-client"
import type { SuccessResponse } from "some-api-client/types"

const [res, err] = await resolve<SuccessResponse>(anAsyncFunction())
if (err) throw err // or handle it in some other way

console.log(res)

or:

resolve() can also take a type parameter for err. When using the default export, this results in err being of type E | Error | undefined, the example below shows how err can be inferred as E. When using the named export and no type parameter is provided, err will be of type unknown. However if a type parameter is provided, it will be of type E | undefined.

import resolve from "resolvjs"
import anAsyncFunction from "some-api-client"
import type { SuccessResponse, ErrorResponse } from "some-api-client/types"

const [res, err] = await resolve<SuccessResponse, ErrorResponse>(anAsyncFunction(), false)
if (err) {
    if ("errorProp" in err) {
        throw err.errorProp
    }
    throw err
}

console.log(res)

Inspiration

Inspiration for this project came from the Fireship short Async Await try-catch hell and uses the solution presented nearly verbatim.