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

gracious

v1.0.0

Published

Facilitate gracious application shutdown by allowing asynchronous code to finish

Downloads

20

Readme

Gracious

Gracious is a library that faciliates the graceful shutdown of Node.js applications.

NPM version NPM downloads Node.js CI Code Climate Test Coverage Code Style gracious Discover zUnit

Why use gracious?

When you deploy a Node.js application, the previous version is usually terminated by sending a SIGINT or SIGTERM signal to the main process. Unless handled, the application will stop abruptly, interrupting any inflight work. Even in well designed systems, failing to complete a unit of work, or attempting to perform it twice, is likely to create problems such has confusing logs, but in poorly designed systems this could result in data loss or inconsistency. By deferring shutdown until inflight work is complete, you minimise these undersireable side effects. This is where Gracious comes in.

How does it work?

Gracious provides a TaskRegistry for tracking inflight units of work. Whenever your application starts a new unit of work you must record it in the registry, then clear the entry when the task completes. In addition, when sent a SIGINT and SIGTERM events, you must prevent the application starting new units of work, and wait for the registry to close. The registry will only close when all inflight units of work are complete, or after a configurable timeout. The default timeout is 3 seconds.

Example Usage

const { globalTaskRegistry: registry } = require('gracious');

const intervalId = setInterval(async () => {
  // Record the start of a unit of work
  const token = registry.register('Example');
  try {
    for (let i = 0; i < 10; i++) {
      await performStep(i);
    }
  } finally {
    // Record that the task has completed
    registry.clear(token);
  }
}, 2000);

['SIGTERM', 'SIGINT'].forEach((signal) => {
  process.once(signal, async () => {
    try {
      console.log(`Received ${signal}`);

      // Stop accepting new work
      clearInterval(intervalId);

      console.log(`Waiting for ${registry.count} task(s) to complete`);

      // Wait for the registry to close
      await registry.close();

      console.log('Done');
      process.exit(0);
    } catch (err) {
      console.error(err);
      process.exit(1);
    }
  });
});

function performStep(i) {
  return new Promise((resolve) => {
    setTimeout(() => {
      console.log(`Performing step ${i + 1}`);
      resolve();
    }, 100);
  }

Good to know

Alternative Usage

Top and tailing tasks between register and clear calls can get onerous, and if the clear call is bypassed, will cause a memory leak. As an alternative consider using the perform function, i.e.

await registry.perform('Example', async () => {
  for (let i = 0; i < 10; i++) {
    await performStep(i);
  }
});

Configurable Timeouts

The default timeout of three seconds can be overriden as follows

// Timeout after five seconds
await registry.close({ timeout: 5000 });

// Disable the timeout completely
await registry.close({ timeout: 0 });

Multiple Registries

Gracious ships with a shared global registry, but you do not have to use it. You can instantiate your own TaskRegistries registry as follows

const { TaskRegistry } = require('gracious');
const taskRegistry = new TaskRegistry();