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

event-custodian

v1.0.0

Published

๐Ÿ“† Take responsibility for listeners on event emitter and look after them

Downloads

10

Readme

event-custodian

Control handlers for an event set on an EventEmitter

Usage

TL;DR

const Custodian = require('event-custodian');
new Custodian(emitter, 'event').mount().on('error', (error) => logger.error(error));

// Example: Avoid errors in events that can cause the process to exit with SIGTERM
new Custodian(process, 'unhandledRejection').mount().on('error', (error) => console.error(error));

Motivation

By overriding native behaviour we can verify existing event handlers run in a safe environment, within a try/catch block. This way we can avoid unexpected results, such as the process exiting unexpectedly within an event handler. We can later decide how we want to handle these errors by placing a general onerror handler on the custodian.

Detailed example using process and "unhandledRejection"

// Reduce all existing listeners to one
const custodian = new Custodian(process, 'unhandledRejection');

// Reduce all existing listeners to one
custodian.mount();

// Handle errors coming up from registered handlers
custodian.on('error', (error) => logger.error(error));

// Add, prepend, remove event handlers as normal
process.on('unhandledRejection', console.error)
    .prependListener('unhandledRejection', (error) => { ... })
    .off('unhandledRejection', console.error)
    .removeAllListeners('unhandledRejection');

// Custodian is now managing the call stack

// Revert to native subscription functions (remove override). Reinstate all existing handlers as individual event handlers
custodian.unmount();

Important note about 'unhandledRejection'

If you use this application to manage unhandledRejection, you must set an on('error') handler. Otherwise the custodian will simply print the errors onto console.error.