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

@jawis/stdio-filter

v5.0.0-dev

Published

Filter the stdio from console applications.

Readme

Stdio filter

Makes it possible to take control over the output from scripts, and define what should be shown in the console.

Installation

npm i stdio-filter

Usage

echo "hello there" | cf

Files

  • cf-all.txt This file will contain all output from the script (filtered, or not). Which is handy if the filtered output was relevant.
  • cf-shown.txt This file will contain the unfiltered output from the script. Which is handy for reviewing the content that can be filtered.

Configuration

Stdio filter will look for the following configuration in the output folder.

  • cf-ignore-prefix.txt The lines in this file will be treated as prefixes, that can be removed from the output.
  • cf-ignore.txt Contains content that should be filtered, and hence not shown. Each line defines a line, that can be filtered.
  • includeJson.js This file must export a function, that returns true or false for a given object. The object is created by parsing lines that contain json data.
  • includeLine.js This function receives each line from the output, and must return a boolean indicating whether to show the line.

Tips

Filter stderr

Stderr is not given to the cf command by default. It's just shown in the console. But it's possible to redirect stderr to stdout, and then it will be filtered.

Here is how it's done in bash:

echo "hello there" 2>&1 | cf

Known issues

  • Output folder is hardcoded.

Related work

License

MIT