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

close_handler

v1.0.1

Published

Do callbacks on node.js app shut down

Downloads

3

Readme

Close Handler

Execute callbacks on node app shutdown

This lib makes easy to execute callbacks when some node app crashes or ends.

This is very useful to avoid locked states for example.

1. Install & configure

$ npm install --save close_handler

2. Create a handler instance

var CloseHandler = require('closer_handler');
var handler = CloseHandler.init();

3. Using handler, register any callbacks to be called on shut down

handler.add(function () {
  // do some code to unlock features
  mongoose.models.Car.update( { }, { $set: { locked: false } }).exec();
});

// or
handler.add(function (err) {
  // a logger
  Logger.log(`App exiting on ${Date.now()} due ${err}.`);
});

Result

When the app for some reason is shut off, each callback will be invoked once and ONLY ONCE!

Deregistering callbacks

Sometimes a block of code, worker or loop ends, and the resources are no longer with a locked state or something similar, thus the callbacks are no longer need, and for that exits a .release( ) instance method:

// empty this handler
handler.release();

This remove all callbacks from that particular instance of the CloseHandler. But there is also a .releaseAll( ) static method:

// empty all handlers
CloseHandler.releaseAll();

This will remove all callbacks from all handlers.

Callback function

If the app crashes, all callbacks function will receive the Error as a first argument. This will be a Error instance. If the app just ends its life cycle, no arguments are passed.

Async code

It's kind of impossible to execute and wait the response from an async function before the execution terminates after the kill signal, besides SIGINT which can be delayed. But you can execute async code if you do not need to do anything with the response. I've tested MongoDb update and insert queries with mongoose, and it works flawless, just call the functions.