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

eslint-filtered-fix

v0.3.0

Published

Gain more control over how ESLint fixes are applied.

Downloads

377,867

Readme

eslint-filtered-fix

npm

This tool allows additional control over the fixes that ESLint makes to your code. It uses the ESLint that you've installed in your project (>=7.0.0), and allows you to specify exactly which rules to fix.

ESLint can save a lot of drudgery by automatically fixing your code to meet the guidelines that you've told it to enforce. But, by using the built-in eslint --fix command, your code can undergo drastic changes, especially if you have recently introduced ESLint or added more rules that are failing. Sometimes, it's better to fix a single rule or a small set of rules at a time, resulting in smaller, more focused commits. That is exactly what you can do with eslint-filtered-fix.

Installation

npm install --save-dev eslint-filtered-fix

or

yarn add --dev eslint-filtered-fix

Also ensure that you have a version of ESLint which is 7.0.0 or newer. If you need to use an older version of eslint, please use version 0.1.X of eslint-filtered-fix.

Usage

Add as an npm script, or run it directly with yarn:

yarn eslint-filtered-fix <filename or dir>

If you do not add any other options, all fixes will be applied, as if you had run eslint --fix on the files you specified.

Options

--rule

Only apply fixes for the rule(s) specified. You can specify multiple rules by adding more than one --rule, or using an array --rule [semi,newline-after-var]. (Notice that spaces in the array are not allowed.)

--no-warnings

If you do not want lint warnings to be autofixed, use the --no-warnings flag. With that flag, only errors will be fixed.

--ext

If your javascript files have an extension other than .js, you can use the --ext flag to specify which extensions to examine. For example, this will fix the semi rule in all files within the lib directory ending in .jsx or .js:

eslint-filtered-fix lib/ --ext .jsx,.js --rule semi

globs

You are not limited to directory and file names as arguments, you can also specify a glob pattern. For example, to examine all .jsx files in "test/" directories within "lib/":

eslint-filtered-fix lib/**/test/**/*.jsx --rule semi

JS API

The fix function can also be required and called from a node.js function. It is an async function, so be sure to await the result.

const { fix } = require("eslint-filtered-fix");

const results = await fix(files, fixOptions, configuration);

Notes

This module does not make any decisions about which ESLint rules to run. Make sure your project has a valid ESLint config file.

For a more interactive experience, check out eslint-nibble.