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

spam

v0.2.9

Published

Wrapper around cluster module to simplify multi-process work

Readme

Simple Process Manager (SPaM)

Version Downloads Build Status Known Vulnerabilities Coverage Status

SPAM is a module for simple node.js process management, and wraps the cluster module. It has nothing to do with email spam.

Use

Yarn is recommended as a package manager, but npm can be used as an alternative.

To install:

# install yarn if required
npm install -g yarn
yarn add spam

To create some processes, using the spawn method. This takes the following parameters:

  • Configuration object
    • number (number of processes to spawn, e.g. 4)
    • timeout (time in milliseconds to allow each spawn to occur, before timing out)
    • strategy (either 'series', or 'parallel', to spawn one at a time, or all together)
    • readyOn (what signal indicates the script is ready, 'ready' or 'listening' - default)
  • Callback when initialization of the module is complete
var spam = require('spam');

// to create 4 processes using the myscript.js script - ready on listen(),
// created in parallel, with a timeout of 60 seconds
spam.setScript('./myscript.js');
spam.spawn(
  {
    number: 4,
    timeout: 60000,
    strategy: 'parallel'
  }, function(err) {
      // callback occurs when all processes have declared they are working
      // or a timeout occurs
      if (err) {
        console.log('oops');
      }
});

// to create 2 processes callback is called when 'ready' message sent, not on 'listen'
// created in series, with no timeout
spam.spawn(
  {
    number: 2,
    timeout: 0,
    strategy: 'serial',
    readyOn: 'ready'
  },  function(err) {
      // callback occurs when all processes have declared they are working
      // or a timeout occurs
      if (err) {
        console.log('oops');
      }
});

If you want to log what's going on in SPAM

spam.on('log', function(message) {
  // do some logging
  console.log('SPAM: ' + message);
});

If you want to gracefully restart all the processes, by starting a new worker before killing the old worker, do this with the restart method.

// graceful restart of all the processes
spam.restart({ strategy: 'series' }, function(err) {
  if (err) {
    console.log('oops');
  }
});

To stop all the processes:

// stop all
spam.stop(function() {
  console.log('stop initiated')
});

NOTE: The scripts that are run, either need to run server.listen() or emit a specific 'ready' message. If they do not do this, then SPAM will assume they've not started and time them out. You can emit a 'ready' message using a convenience function or explicitly using process.send();

// using the signal module
var signal = require('spam').signal;
signal.ready();

// using the process.send method
process.send({ cmd: 'ready'});

Tests

To run the npm unit tests, install development dependencies and run tests with 'npm test' or 'make'.

# clone repo and install dependencies
git clone [email protected]:iandotkelly/spam.git
cd spam
yarn
# run tests
yarn test

Coverage can be measured after running the tests, and an html coverage report is written in the coverage/lcov-report directory:

open coverage/lcov-report/index.html

If you contribute to the project, tests are written in mocha, using should.js or the node.js assert module.