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 🙏

© 2025 – Pkg Stats / Ryan Hefner

serverrunner

v0.8.0

Published

Start node servers and keep them running.

Downloads

21

Readme

serverrunner

serverrunner starts node servers and then keeps them running. Allows for graceful shutdowns.

Installation

npm install serverrunner

Usage

var serverrunner = require('serverrunner');

In the simplest case, serverrunner can be called with an options parameter with the following properties:

serverrunner({
    workers: 4,
    port: 80,
    server: "../server/app.js",
    watch: "../",
    disgraceful: false,
    allowForcedExit: false,
    app: {
        // Application config
    }
});
  • workers The number of worker processes to create. A reasonable value is the number of processor cores on the server.

  • port The starting port number for worker processes to listen in on. Each subsequent worker will listen on the next port number. eg: if workers is set to 4 and port is set to 80, then the 4 workers will listen on 80, 81, 82, and 83 respectively.

  • server The path to the file which will ultimately be require()'d by the worker processes. The path should be relative to the current working directory of the entry script. An absolute path works too. This file is expected to export a function that accepts a config parameter (the contents of app) and should return an express object.

  • watch This path will be watched for file changes and will trigger a server restart.

  • disgraceful Helpful during development so that the server can be restarted or shut down instantly.

  • allowForcedExit Waits for open connections to finish before shutting down or restarting but gives the option not to wait.

  • app Config options that will be passed to the app server.

Another way to use serverrunner is to pass a path to a .cjson file which contains a config as given above.

serverrunner('config/development.cjson');