A CLI tool that groups ESLint errors by rule and provides per-rule actions like auto-fix and disable comments to efficiently handle large linting outputs.
eslint-interactive is a CLI tool that wraps ESLint to help developers efficiently handle large numbers of linting errors. It groups errors by rule and provides per-rule actions like auto-fixing, adding disable comments, and applying suggestions. The tool solves the problem of overwhelming ESLint output when introducing new rules or making config changes.
JavaScript and TypeScript developers working on projects with extensive ESLint configurations, especially those introducing ESLint to a codebase or making significant rule changes.
Developers choose eslint-interactive for its granular per-rule control, which allows safe and efficient fixing without the risks of bulk auto-fixes. It offers a faster and more intuitive workflow compared to similar tools by leveraging ESLint's native APIs and providing a programmable interface for advanced use cases.
The CLI tool to fix huge number of ESLint errors
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Groups ESLint errors by rule and allows per-rule actions like auto-fixing, disabling comments, and converting errors to warnings, enabling safe and targeted fixes without risking bulk changes.
Provides a formatted breakdown of fixable problems per rule with counts, helping developers quickly assess the scope of issues when introducing new rules or configs, as highlighted in the motivation.
Offers a programmable API to apply ESLint suggestions and force fixes on normally unfixable problems, giving advanced users customization beyond standard ESLint capabilities, as documented in the Programmable API section.
Includes tricks to speed up the auto-fix cycle per-rule compared to similar tools like eslint-nibble, leveraging ESLint's native APIs for reliability without additional parsing config.
Global installation is not recommended and only supported on a best-effort basis due to potential resource access issues with locally installed ESLint, forcing users to install it locally in each project.
Requires specific Node.js and ESLint versions, and flat config for the latest releases, which can block adoption in projects with older or incompatible setups, as noted in the Requirements section.
Admits in the FAQ that inserting disable comments is slower than tools like suppress-eslint-errors because it uses ESLint's sequential API instead of parallel processing, impacting performance on large files.
The programmable API for applying suggestions and forced fixes requires writing JavaScript code, adding a learning curve and setup overhead for users who just want simple, out-of-the-box fixes.