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

failsafe-promises

v1.1.3

Published

failsafe-promises makes it impossible for promises to throw an exception. This makes management (hopefully) easier

Downloads

4

Readme

failsafe-promises

This small package is meant to be a shorter syntax for handling rejected promises (or promises that could reject). By using this package you can still check for the result/success of a promise, but there is no need for try-catching it anymore.

How to use:

Importing

I personally suggest to import with the as syntax, so you can keep the naming short.

Example:
import { failSafe as fsp } from 'failsafe-promises';

or

import { failSafe as __ } from 'failsafe-promises';

Usage

The imported (async) function is a wrapper for a normal promise. So, just pass your promise into it:

Example:
// Wrapping a database-promise, which now can never again kill your runtime-app by rejecting
const result = await fsp(DB.someQuery());

Result

What you are getting back from wrapping the promise is an object that has the following structure:

internalPromise: Promise<type of input-promise>
success: boolean
error: null or rejection-error of input-promise
result:  null or type of input-promise

So what you can do as an example is:

import { failSafe as fsp } from 'failsafe-promises';

const query = await fsp(DB.someQuery());
if (query.success) {
    console.log('result=', query.result);
} else {
    console.log('result=', query.error);
}

If you are not interested in the case of an error and are only interested in if the promise has a not-null value or is null/error, you could use the ES6 destructuring syntax:

import { failSafe as fsp } from 'failsafe-promises';

const { result } = await fsp(DB.someQuery());
console.log('result=', result);

or even

import { failSafe as fsp } from 'failsafe-promises';

if ( (await fsp(DB.someQuery())).success ) {
    console.log('query was ok');
}

Plans for the future

I'm not sure if the idea of this package sounds interesting for others, but i could implement some global settings for this package, like logging errors (bool-flag for example) or passing a custom error-handler.

If you have any idea, what could be added/changed, just create an issue on github :)