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

resurrector

v0.0.3

Published

automatically resurrect processes based on heartbeat signal

Downloads

6

Readme

Resurrector

Automatically resurrect processes based on heartbeat signal

It's easy to detect process crash, but hard to detect when it hangs without quitting. Resurrector uses heartbeat through OSC to automatically restart process that stopped responding.

Usage

  1. npm install -g resurrector
  2. write config.json
  3. resurrector config.json

Sample config

{
  "port": 4000,
  "interval": 100,
  "path": "/hb/",
  "processes": [
    { "id": "app 1", "cmd": "node app1.js", "timeout": 2000 },
    { "id": "app 2", "cmd": "node app2.js", "timeout": 5000 }
  ]
}

Main config

  • port - OSC port that resurrector listens on (defaults to 3000)
  • interval - how often resurrector checks for heartbeat (defaults to 100ms)
  • path - OSC path to send heartbeat on (defaults to /hb/)
  • processes - array of processes to start

Process config

  • id - process name, required
  • cmd - command to run
  • timeout - how long to wait before restarting

Heartbeat

Each of the running processes should periodically ping resurrector with OSC message on specified port and path, sending the process id (from config) as only parameter. So for the sample config, process 1 sends: /hb/ "app 1" on OSC 4000, and process 2 sends: /hb/ "app 2" on OSC 4000.