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 🙏

© 2023 – Pkg Stats / Ryan Hefner

compare-eslint-configs

v1.1.1

Published

Compares ESLint configs

Downloads

13

Readme

Compare ESLint configs

npm version npm downloads js-semistandard-style ES Module Ready Badge Types in JS

Usage

npm install -g compare-eslint-configs
compare-eslint-configs .eslintrc new.eslintrc

Or simply:

npx compare-eslint-configs .eslintrc new.eslintrc

Example

CLI output

npx compare-eslint-configs new.eslintrc -t cli.js

CLI output

Markdown output

npx compare-eslint-configs new.eslintrc -t cli.js -m

Only active in some:

Mixed severities:

Mixed configs where otherwise okay:

  • no-console
    • new.eslintrc:
      [{"allow":["warn","error"]}]

Syntax

compare-eslint <eslint config files, separated by spaces>

If a single config file is given, then it will be assumed to be compared with .eslintrc.

More than two config files can be compafred at once.

Flags

  • -r / --group-rules – when set the comparison output will group by rules rather than config
  • -t <file> / --target-file <file> – defaults to index.js – the file for which the config will be compared. Especially important when there's eg. different configs for .js and .ts files. Then point this to the one you want to do a comparison on.

See also