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

eslint-explainer

v1.0.1

Published

eslint rules explainer

Downloads

15

Readme

ESLint Explainer

ESLint explainer is a tool to quickly display the current project eslint rules and their explanation

Installation and Usage

Install the package globally using npm:

$ npm install -g eslint-explainer

After that, you can run ESLint on any project ( eslint and all the config need to be installed locally )

Simply run, in the project root folder :

$ eslint-explainer

Example output (for the webpack project):

{
  "strict": 0,                       // require or disallow strict mode directives [AUTOFIX]
  "camelcase": 0,                    // enforce camelcase naming convention
  "curly": 0,                        // enforce consistent brace style for all control statements [AUTOFIX]
  "indent": [                        // enforce consistent indentation [AUTOFIX]
    2,
    "tab",
    {
      "SwitchCase": 1
    }
  ],
  "eol-last": 1,                     // require or disallow newline at the end of files [AUTOFIX]
  "no-shadow": 0,                    // disallow variable declarations from shadowing variables declared in the outer scope
  "no-redeclare": 2,                 // disallow variable redeclaration [RECOMMENDED]
  "no-extra-bind": 1,                // disallow unnecessary calls to .bind() [AUTOFIX]
  "no-empty": 0,                     // disallow empty block statements [RECOMMENDED]
  "no-process-exit": 1,              // disallow the use of process.exit()
  "no-underscore-dangle": 0,         // disallow dangling underscores in identifiers
  "no-use-before-define": 0,         // disallow the use of variables before they are defined
  "no-undef": 2,                     // disallow the use of undeclared variables unless mentioned in /*global */ comments [RECOMMENDED]
  "no-unused-vars": 0,               // disallow unused variables [RECOMMENDED]
  "consistent-return": 0,            // require return statements to either always or never specify values
  "no-inner-declarations": 1,        // disallow variable or function declarations in nested blocks [RECOMMENDED]
  "no-loop-func": 1,                 // disallow function declarations and expressions inside loop statements
  "space-before-function-paren": [   // enforce consistent spacing before function definition opening parenthesis [AUTOFIX]
    2,
    "never"
  ]
}

You can additionally specify a specific file (in case of multiple, nested, eslintrc config file in the same project)

$ eslint-explainer <filename>