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 🙏

© 2026 – Pkg Stats / Ryan Hefner

signalmanager

v1.0.8

Published

ES6 JS class to capture exit signals and specify callbacks to accept or deny them

Downloads

10

Readme

signalmanager

ES6 JS classes for socket client and server message passing

Installation

npm install signalmanager --save

Usage

Prevent closing until your code approves it

Add shutdown handlers for SIGINT and SIGTERM.
This is in case multiple "threads" or classes need to
do individual checks before closing. (Obviously no program can withstand SIGKILL though)

Add a request handler first. It will be responsible for passing into the
callback true or false for if it approves the shutdown.
If all processes approve, all shutdown handlers are run then exited.
If any function/class passes false for REJECTION, the shutdown is canceled;
and no shutdown handlers are run.


// SignalManager singleton. Should be same variable required anywhere
var SignalManager = require('signalmanager');

// APPROVAL HANDLER
// Generally the idea is that each service should have a shutdown approval handler to
// ask each service before shutting down if it can safely
SignalManager.addShutdownApprovalHandler(() => {
  if (somethingImportantHasNotFinishedYet) {
    return false; // do not approve shutdown. will cancel node program shutdown
  } else {
    return true; // will allow next handlers to run and if all approve, move on to the ShutdownHandlers
  }
});

// SHUTDOWN HANDLER
// If all the approvalHandlers returned true, shutdown will begin. All shutdownHandlers
// will be called in order of adding. Generally
SignalManager.addShutdownHandler(() => {
  if (isAnEmergencySomethingImportantIsStillRunning) {
    // false here as opposed to in the approval handler probably signifies something important
    // because by this point, other of the shutdown handlers may have run
    return false; // do not approve shutdown. will cancel program shutdown
  } else {
    // these are examples of what you would do
    someSocket.close();
    someFile.close();
    someEmail.send();

    return true; // will allow next handlers to run. Upon all returning true, it will allow exit
  }
});

Credits

http://c-cfalcon.rhcloud.com