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

safe-promises

v0.2.0

Published

Promises that enforce catching.

Downloads

7

Readme

Build Status npm version

Safe Promises in JavaScript

Promises go wrong too often.

  • It's too easy to forget to catch a promise.
  • Sometimes promises just stop in their tracks.

SafePromise doesn't let you forget, and makes sure to time out with an error.

Installation

Just run:

$ npm install --save safe-promises

Examples

By splitting the construction of the promise pipeline from the execution, we can ensure that we always pass in a final catch handler. It looks something like this:

let safePromises = require('safe-promises');

let SafePromise = safePromises.timeOutAfter(1000).failWith(console.error);

new SafePromise((resolve, reject) => resolve(5))
    .then((value) => {
        if (value % 2 == 1) {
            throw new Error('No odd numbers allowed.');
        }
        return value;
    })
    .perform();

That will fail, and even though we haven't provided an explicit catch for the promise, we've constructed it with a failure handler that logs to console.error, so we know we'll never have to worry about it.

If you need different sorts of error handlers, just construct different SafePromise classes. Here, we're setting a timeout of 5 seconds, after which the default timeout error will be passed to the error handler instead.

let UIPromise = safePromises.timeOutAfter(5000).failWith((error) => {
    $('#error').text(error.message).show();
});

UIPromise.resolve(user.name)
    .then(lookupUser)
    .perform();