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

process-keep-alive

v0.0.1

Published

A simple module using cluster to force your process running permanently.

Downloads

11

Readme

A simple module using cluster to force your process running permanently.

Important notes before you use the module

  1. The main file, that is, your application, you need to configure in the different file, like keepalive.js, for example, and run with node the keepalive file.
  2. Connection and process are very different things. Be that in mind.
  3. If your machine(including servers) is down, it is clear that this module will not work.
  4. If you shutdown the process using ctrl + c or pm2 stop, pm2 restart, the actions that trigger the "SIGINT" signal, the module will not resurrect the workers.
  5. If you send a shutdown message to the master process using process.send({ message: "shutdown" }), the cluster will shutdown all worker processes, and if you define the worker to shutdown by sending process.send({ message: "shutdown", worker: 0 }), it will only shutdown in that worker.
  6. If you send process.send({ message: "shutdown-all" }), the cluster will shutdown all workers processes.
  7. The KeepAlive module will alert a error message and close the process if you try to run the KeepAlive Cluster in worker process.

Install

Install with npm or yarn

$ npm i process-keep-alive --save
$ yarn add process-keep-alive

Usage

  • main.js
const { Cluster } = require("process-keep-alive")
const cluster = new Cluster({
    /**
     * @param {string} mainFile - Defines which file the cluster will run. 
     */
    file: `${process.cwd()}/test.js`, 
    /**
     * @param {object} env - Defines the environment variables that will be used by workers. Default: process.env
     */
    env: process.env,
    workerCount: 1
})

cluster.init()
  • test.js
setTimeout(() => undefinedMethod(), 10000)

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue

Author

zero734kr

License

Copyright © 2020 제로ㅣBrazil Licensed under the MIT license.


This file was generated by readme-generator on January 22, 2020.