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 🙏

© 2026 – Pkg Stats / Ryan Hefner

lil-pids

v2.6.1

Published

Dead simple process manager with few features

Readme

lil-pids

Dead simple process manager with few features

npm install -g lil-pids

omg

First create a file with the commands you wanna have running

# assuming this file is called 'services'
node server.js
node another-server.js

Then simply start lil-pids with the filename

lil-pids ./services

It'll watch the file so every time you update it, old processes no longer referenced from the file will be shutdown and any new ones will be spawned.

lil-pids will forward all stdout, stderr to its own stdout, stderr prefixed with the process id.

It will also tell you when a command has been spawned, exited and finally it will restart processes when the crash/end.

lil-pids can also write the pids of the current running processes to a file. Just pass the pids filename as the 2nd argument

lil-pids ./services ./pids

Then you can simply cat ./pids to see what is running at the moment.

That's it!

Pro-tips

  • Spawn lil-pids ./services ./pids with your OS' service monitor. Then it'll startup at boot and every thing you need to do is edit the services file.

  • Add > output.log and 2> errors.log to the end of a command to persist logs to files.

  • Cat the pids file and use kill to restart a running process. Use ps / top to check how something is running.

  • Add # in front of a service to disable it temporarily.

Start on server boot

To start lil-pids on server boot (or restart it when it crashes) you can add it using systemd.

npm install -g add-to-systemd
sudo $(which add-to-systemd) -u $(whoami) -e PATH=$PATH lil-pids $(which lil-pids) ./services ./pids
sudo systemctl start lil-pids

License

MIT