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

web-pm2

v0.0.5

Published

PM2 Web interface

Readme

web-pm2

PM2 Web interface.

Image of web-pm2

Usage

  1. Install: npm install -g web-pm2

  2. Run: web-pm2

  3. enter: http://localhost:3666/

Add processes to control (both pm2 and other)

web-pm2 controls the current running pm2 processes.

To control pm2 processes that are not running you only need to add them into processes directory.

How?

create a directory with the name of the process in processes directory, create an index.js file within the new directory.

The index.js file should follow this interface:

it should export an object with the following functions and attributes (all functions should return a promise):

pm2, start, stop, restart, status, describe, getConfigurations, setConfigurations

An example:

module.exports = {
  pm2: false,
  start: function(){...},
  stop: function(){...},
  restart: function(){...},
  status: function(){...},
  describe: function(){...},
  getConfigurations: function(){...},
  setConfigurations: function(){...},
}

you can find more examples in processes directory that comes with the repo.

Startup processes

You can add a configuration file that will start up pm2 processes at the start of web-pm2

  1. Create a directory named config on the web-pm2 root directory

  2. Create a json file with the name of the environment as an example use default.json (using the config module)

  3. The file will contain processes names as shown here, they should have the same name as the directory name:

{
  "processes": ["mongo",  "nginx",  "vnext",  "iis"]
}

TODOS

  • [ ] system actions should be on the app bar.
  • [ ] hide buttons when disabled.
  • [ ] process dependency handling.
  • [ ] versioning of processes to show app on main screen (+its own).
  • [ ] more abilities of processes through plugins.
  • [x] refresh should be on the app bar.
  • [x] enabling logs.
  • [x] search on the right end.
  • [x] left of it the system actions and the refresh.
  • [x] on the left end the process actions.
  • [x] uptime in general info should be fixed.
  • [x] uptime in the table should be fixed.
  • [x] created on in the table should be fixed.
  • [x] implement search logic by app name, pm2 id, pid.
  • [x] control processes out of pm2 reach.
  • [x] configuration manager for processes.