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-error-suppressor

v1.1.1

Published

Suppress flow errors from `node_modules`.

Downloads

41

Readme

flow-error-suppressor

This is an alternative to jbreckel's flow-result-checker for *flow issue 869 that does not alter the text styling of flow's error output and does not have any dependencies, so to speak: It expects the raw output, which can be provided by using the script command. This has been tested only on OS X.

In package.json:

"scripts": {
  "flow": "script -q /dev/null flow --show-all-errors | flow-error-suppressor"
}

The output will include the number of errors that are shown and that have been suppressed:

Found 10 errors
      2 suppressed
      8 shown

*We should not have to worry about flow errors reported for third party modules (i.e. from node_modules). However, it is often the case that one cannot simply [ignore] a problem module without having provided a libdef, which can be very time-consuming if it is not included in flow-typed.

Options

By default, only unsuppressed errors will result in an exit status of 2.

-a --error-on-any

Exit with 2 if there are any flow errors, regardless of origin.

-n --no-error

Always exit with 0. This is useful if you don't want npm run flow to have that "stupid npm error" and if you want to pass arguments to flow at the same time (i.e. no more || true or ; exit 0 getting in the way).

All but the first option provided will be ignored.