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

prefix-cli

v1.2.0

Published

Mechanism for prefixing output from multiplexed cli applications

Downloads

197

Readme

prefix-cli

What?

Mechanism for prefixing output from multiplexed cli applications

Why?

If you have, for example, a repository hosting a client and api applications, perhaps you'd like to use npm-run-all, particularly run-p to start up all parts of the system, running in parallel. In this case, it gets a little difficult to discern which output is coming from where. To solve this ambiguity, it would be nice if lines from each process' output were prefixed with something easily recognisable. Enter pre

Usage

some-process | pre {label} {color}

where

  • label is any text you'd like to prefix lines with
  • color is any color understood by chalk
    • color is optional and will default to white

Example please?

prefix-cli installs a cli application, called pre, which will echo any input it receives on stdin with the provided prefix, optionally colored with the provided color. For example, we may have started with a scripts section like this in our package.json:

{
    "scripts": {
        "start-server": "cd server && npm start",
        "start-client": "cd client && npm start"
    }
}

so we install npm-run-all so that we can launch both commands with one script:

{
    "scripts": {
        "start-server": "cd server && npm start",
        "start-client": "cd client && npm start",
        "start": "run-p start-server start-client"
    },
    "devDependencies": {
        "npm-run-all": "^4.1.5"
    }
}

and now our two commands are started simultaneously, with their outputs multiplexed on the terminal. To disambiguate their outputs, we could install and use prefix-cli:

    "scripts": {
        "start-server": "cd server && npm start | pre server yellow",
        "start-client": "cd client && npm start | pre client green",
        "start": "run-p start-server start-client"
    },
    "devDependencies": {
        "npm-run-all": "^4.1.5",
        "prefix-cli": "^1.0.0"
    }

and then we would see lines like:

This works on the big three platforms (and most likely on others too)