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

daemonspawn

v1.0.1

Published

JS api to spawn daemons, check their status, and kill them

Downloads

477

Readme

daemonspawn

spawn daemon processes, check their status, and kill them

js usage

var daemon = require('daemonspawn')

var proc = daemon.spawn(cmd, opts)

spawns a daemonized process by spawning cmd with opts using npm-execspawn, which has the same interface as child_process.spawn

returns proc, the child process. you need to remember proc.pid in order to use the other methods, usually people save it to a file, but any method will work.

daemon.status(pid, cb)

checks if pid is running, calls cb with (error, running) where running is a boolean

daemon.kill(pid, cb)

SIGKILLs the pid, calls cb with (err)

cli usage

$ npm i daemonspawn -g

$ daemonspawn
Usage:    daemonspawn <spawn,status,kill> [args..]

spawn     spawns a daemon, prints pid to stdout
status    given a pid of a daemon, checks if daemon is running or not
kill      given a pid of a daemon, kills the daemon with SIGKILL

$ daemonspawn spawn node server.js
3762

$ daemonspawn status 3762
daemon is running

$ daemonspawn kill 3762
daemon has been killed

$ daemonspawn status 3762
daemon is not running