Analyze ESLint configurations to list current, available, unused, and deprecated rules.
eslint-find-rules is a Node.js utility that analyzes ESLint configuration files to list configured rules, all available rules, unused rules, and deprecated rules. It helps developers maintain and audit their ESLint setups, ensuring they leverage the full rule set and avoid outdated practices.
Developers and teams creating or maintaining shareable ESLint configurations, such as those building custom style guides or internal linting standards.
It automates the tedious process of auditing ESLint rules, providing clear insights into configuration gaps and deprecated usage, which saves time and improves code quality enforcement.
Find built-in ESLint rules you don't have in your custom config
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Lists all available, configured, unused, and deprecated rules in one tool, making it easy to audit and clean up ESLint configs, as shown in the README's support for multiple options like -a, -c, -d, and -u.
Separately analyzes rules from ESLint plugins using the -p option, helping teams manage extended linting setups without mixing core and plugin rules.
Includes a built-in diff tool to compare rules between two configuration files, aiding in updates and migrations, as highlighted in the 'eslint-diff-rules' script example.
Provides a Node.js API for embedding rule analysis into build scripts or custom tooling, allowing automation in CI/CD pipelines, as demonstrated in the 'As a require'd module' section.
Relies on ESLint plugins correctly marking deprecated rules in metadata, which isn't always guaranteed, as the README admits by asking users to file pull requests for non-compliant plugins.
Cannot be used globally without installing ESLint and all referenced plugins globally, limiting flexibility for ad-hoc audits and increasing setup complexity.
Designed for batch processing of configuration files rather than providing immediate linting feedback during development, making it less useful for on-the-fly rule checks.