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

amaster

v0.0.1

Published

Just a (cluster) master process for Node.js.

Downloads

5

Readme

node-amaster

Just a (cluster) master process for Node.js.

Install

npm install amaster

Usage

node node_modules/amaster [ path/to/config.json ] [ stop | reload | kill | clean ]

Default config: config.json.

Config

  • log - path to log file. Default: null, stdout.

  • errorLog - path to error. Default equals to log.

  • pid - path to pid file. Required for stop reload kill clean commands.

  • consoleMode - if set to true, process will not be daemonized. Default: false.

  • cwd - working directory. Default: current dir.

  • killTimeout - time in ms of waiting process termination before kill. Default: 5000.

  • killCheckInterval - time in ms of checking interval for stop and kill commands. Default: 200.

  • forkRateTimeout - time in ms to check fork rate. Default: 1000.

  • forkRateLimit - max allowed fork count in forkRateTimeout interval. Default: null, workers count.

  • user - worker user. Default: null, current user.

  • group - worker group. Default: null, current group.

  • worker - worker module. Default: worker (worker.js in cwd directory). Must export function:

      module.exports = function(options) { /* ... */ }
  • workers - count of workers or workers options. Default: 1.

    You can specify array of options objects for each worker, these options will override user, group, worker or any additional options for every worker.

      {
          "worker": "myworker.js",
          "host": "localhost",
          "workers": [
              { "port": 8001 },
              { "port": 8002, "worker": "anotherworker.js" }
          ]
      }

    You can specify object with length property and any numeric properties (like an array) to override options in some workers, and use main options in others.

      {
          "worker": "myworker.js",
          "host": "localhost",
          "port": 8000,
          "workers": {
              "length": 5,
              "4": { "port": 8001, "worker": "anotherworker.js" }
          }
      }

    You can specify count of workers, in this case all workers will have same options.

      {
          "worker": "myworker.js",
          "host": "localhost",
          "port": 8000,
          "workers": 4
      }