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 🙏

© 2025 – Pkg Stats / Ryan Hefner

noreman

v0.0.0

Published

package.json-based process manager

Readme

noreman

noreman is a package.json-based process runner for Node. It's extremely experimental at this time, so I can't recommend using it outside of the development environment.

Install

$ npm install -g noreman

Use

Let's say that in development I need to watch and compile CoffeeScript and Sass files, as well as run a web server. In production, I might just need to run a web server. With noreman, I can achieve this with a "processes" section in my package.json:

{
  "name": "my-npm-module",
  "processes": {
    "development": {
      "coffee": "coffee -o js -cw coffee",
      "sass"  : "sass --watch scss:css",
      "web"   : "bin/web",
    },

    "production": {
      "web": "bin/web"
    }
  }
}

Now, if I run noreman from the directory my package.json is in, noreman will start the three defined processes, and log their output to standard out, prefixed by a color-coded label for each process:

noreman output

Environment Resolution

If passed an environment name, noreman will use that environment, e.g.:

$ noreman development

If not given an argument, noreman will look for NODE_ENV in the current environment (it will source your .env file first for you) and use that.

If not given an argument, and unable to see NODE_ENV, noreman will default to "development".