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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@ianvs/eslint-stats

v2.0.0

Published

A package of custom formatters that show aggregated stats of eslint errors

Downloads

344,722

Readme

Coverage Status Build Status

#Statistic Reporter for ESLint. Analyses the files for error frequency, rather than location. This is helpful when introducing ESLint to an existing project.

Forked from https://github.com/ganimomer/eslint-stats

screenshot

Install

npm install --save-dev eslint-stats

Getting Started

Use it with grunt:

...
  eslint: {
    options: {
      format: require('eslint-stats').byError,
      src: [...]
    },
...

or use it directly with ESLint:

$ eslint --format node_modules/eslint-stats/byError.js

Available Reporters:

byError

Shows the eslint report, aggragated by errors, without separation into specific files. Rules with warnings are not displayed

byWarning

Shows the eslint report, aggragated by warnings, without separation into specific files. Rules with errors are not displayed.

byErrorAndWarning

Shows the eslint report, aggragated by errors and warnings, without separation into specific files. Errors are red, and warnings are yellow.

byErrorAndWarningStacked

Shows the eslint report, aggragated by errors and warnings, without separation into specific files. Errors are red, and warnings are yellow. If any rule is an error in one file and a warning in another, results show up stacked.

byFolder

Shows the eslint report, aggragated by errors and warnings, separated into folders. Errors are red, and warnings are yellow.