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

caught

v0.1.3

Published

Avoids UnhandledPromiseRejectionWarning and PromiseRejectionHandledWarning

Downloads

9,025

Readme

node caught

npm install Build Status Dependencies Status Known Vulnerabilities Downloads License

This module lets you attach empty rejcetion handlers to promises to avoid certain warnings that will be fatal errors in next versions of Node.

Since version 0.1.0 it supports TypeScript thanks to Wil Lee.

For a version for Deno, see: https://deno.land/x/caught

More info

Doing something like this:

var p = Promise.reject(0);

setTimeout(() => p.catch(e => console.error('caught')), 0);

will generate a lot of helpful warnings:

(node:13548) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): 0
(node:13548) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:13548) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)

This module lets you write:

var p = caught(Promise.reject(0));

setTimeout(() => p.catch(e => console.error('caught')), 0);

to ignore those warnings on a per-promise basis.

Use at your own risk.

Background

For more info see this answer on Stack Overflow:

Installation

To use in your projects:

npm install caught --save

Usage

var caught = require('caught');

var p = caught(Promise.reject(0));

Note that it is not the same as writing:

var p = Promise.reject(0).catch(() => {});

which would not return the original promise and wouldn't let you add catch handlers later.

Issues

For any bug reports or feature requests please post an issue on GitHub.

Author

Rafał Pocztarski Follow on GitHub Follow on Twitter Follow on Stack Exchange

Contributors

License

MIT License (Expat). See LICENSE.md for details.