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

nproc

v0.0.5

Published

A process management console written in Node.js

Downloads

5

Readme

nproc

Node-based Process Manager

nproc provides a node-based microserver to allow browser-based definition and management of a set of processes.

The idea behind nproc is to be able to have a set of processes, such as your database and other services controllable from a single place.

Screenshot

Screenshot

Installation

npm install -g nproc

Usage

From any command-line console type:

nproc

This will start the microserver on port 3000.

Now you can start up your browser at http://localhost:3000. Note that if you have the name or IP address of the machine that nproc is running on, you can access it remotely (this can be both good and bad, see Uncle Ben below).

Defining Processes

Click the green "+ add new service" link and fill out the resulting form:

  • Name: the human-readable title of this process
  • CWD: the working directory that the process will use
  • Command Line: the executable and arguments to run

Obviously, "Save Changes" will save your changes and add the process to the list, "Cancel" will cancel your changes.

Starting / Stopping a Process

Clicking on the "Start" button next to the service title will start the process. The service list item will turn green while it is running, and the "Stop" button will replace the "Start" button. Remember the process is running inside the node microserver and will continue running as long as the microserver is running, regardless if you close your browser.

Viewing a Process

Clicking on the service title name will bring up a view of the output console for the process on the right. It is updated every two seconds.

Editing / Deleting a Process

Clicking on the menu lines on the right end of the service title will open up the options for that service. There will be the three textboxes which will allow you to change their values. Note that changing anything except the "name" field will have no effect until the process is restarted.

In addition there is a "delete" button for deleting the service from your list. Note that this will not ask you to confirm and will instantly erase your service. It will attempt to stop the service first.

Saving

Whenever you press a "Save Changes" button, whether while adding or modifying settings, it is saved to disk in a "services.json" file in the directory that nproc is run from.

Uncle Ben

I am so very sorry but I have to say this:

"With Great Power... Comes Great Responsibility"

This allows anyone who can ping your machine to arbitrarily define processes and execute them. It is YOUR responsibility to make sure that you are taking the precautions that are appropriate for your environment!