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

flow-result-checker

v1.1.0

Published

A package to avoid reporting errors in `node_modules`.

Readme

flow-result-checker

Build Status Build Status npm version

This is a small helper script, that parses flow output and filters errors inside node_modules. Afterwards returns the normal flow output for errors inside your package.

You can choose to store the whole result as a txt file by specifying a directory to save the results to.

Options

| option | result | default | |---|---|---| | -d, --dir | specifies the directory where files should be saved. if not specified, files will not be saved | undefined | | -f, --file | name of the file where results are saved | results.txt | | -e, --error-file | name of the file, errors during script execution will be saved | errors.txt |

Examples

Your package.json:

  "scripts": {
    "flow": "flow check --show-all-errors | flow-result-checker",
    "flow-with-save": "flow check --show-all-errors | flow-result-checker -d ./flow"
  },
  "dependencies": {
    "flow-bin": "x.x.x"
  }

with npm:
npm run flow will only print errors in your code
npm run flow-with-save will print errors in your code, but save the whole result in ./flow/results.txt

with yarn:
yarn flow will only print errors in your code
yarn flow-with-save will print errors in your code, but save the whole result in ./flow/results.txt