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

@uphold/process-manager

v4.0.0

Published

A module for handling the lifecycle of a node process

Downloads

20,699

Readme

process-manager

A node.js process manager. This package handles a process's lifecycle, from running to exiting, by handling errors and exceptions, as well as graceful shutdowns.

Status

NPM version CI

Installation

Install the package via yarn:

❯ yarn add '@uphold/process-manager'

Or npm:

❯ npm install '@uphold/process-manager' --save

Usage

To use process-manager simply require it in your project.

const processManager = require('process-manager');

// async/await
processManager.once(async () => {
  await foo.bar();
});

// Promise
processManager.once(() => new Promise((resolve, reject) => {
  foo.bar(err => {
    if (err) return reject();

    return resolve();
  });
}));

And it will now manage your node process.

loop(fn, [options])

This lifecycle is used to loop over a given function.

Arguments

  • fn (Function): the function to run.
  • [options] (object): the options object.
  • [options.interval=0] (integer): how long to wait (in miliseconds) before restarting the function.

Example

const processManager = require('process-manager');

processManager.loop(async () => {
  console.log(await client.getSomeInfo());
}, { interval: 600 });

on(fn)

This lifecycle is used to get a function suited for using with an event emitter. It does not exit unless something goes wrong.

Arguments

  • fn (Function): the function to run.

Example

const processManager = require('process-manager');

async function handler(value) {
  console.log(await client.getInfo(value));
}

client.on('event', processManager.on(handler));

once(fn)

This lifecycle is used to a given function and exit.

Arguments

  • fn (Function): the function to run.

Example

const processManager = require('process-manager');

processManager.once(async () => {
  await client.doWork();
});

shutdown([args])

This function can be called to trigger a process shutdown. If passed an error as an optional argument, it will save it to the errors array. This function will only start the shutdown process once, any extra calls will be ignored, although it will still save the error if one is passed.

If called with { force: true } it will skip waiting for running processes and immediately start disconnecting.

Arguments

  • [args] (object): the arguments object.
  • [args.error] (Error): an error to add to the errors array.
  • [args.force] (Boolean): a boolean that forces the shutdown to skip waiting for running processes.

Example

const processManager = require('process-manager');

processManager.shutdown({ error: new Error('Error') });

Hooks

Currently there are three hooks that can be used to call external code during the shutdown process. If a hook takes longer than 30 seconds to return, it will timeout and continue with the shutdown process.

drain

This hook is called during shutdown, after all running processes have stopped. It should be used to drain connections if the process is running a server.

disconnect

This hook is called after drain and it's where handlers should be added to close running services (ex.: database connections, persistent connections, etc).

exit

This hook is called right before the process exits. It passes an array of errors as an argument to the handler function, and should be used to handle errors before exiting.

addHook({ handler, type, [name='a handler'] })

This function is used to add a hook for one of the types described above.

Arguments

  • args.handler (Function): a function that returns a value or a thenable.
  • args.type (string): the hook type.
  • [args.name='a handler'] (string): identifies the hook.
const processManager = require('process-manager');

processManager.addHook({ handler: () => 'result', type: <hook-type> });
processManager.addHook({ handler: () => Promise.resolve('result'), type: <hook-type> });

Integrations

sentry.io

The recommended way to report errors to sentry is by adding an exit hook and sending each error using a promisified captureException.

const Promise = require('bluebird');
const raven = Promise.promisifyAll(require('raven'));

raven.config('https://******@sentry.io/<appId>').install();

processManager.addHook({
  handler: errors => Promise.map(errors, error => raven.captureExceptionAsync(error)),
  name: 'sentry',
  type: 'exit'
});

Debug

Enable verbose debugging by configuring your own logger and passing it to proccessManager.configure({ log: myCustomLogger }).

The minimum requirements for it to work is that the logger must be Object-like and have functions assigned to properties info, warn, and error. The functions should be able to handle two different argument signatures:

  • log.(message)
  • log.(fields, message)

Most javascript loggers should use this format (this one was derived from bunyan)

Release

The release of a version is automated via the release GitHub workflow. Run it by clicking the "Run workflow" button.

Test

To test using a local version of node, run:

❯ yarn test

License

MIT