Feature Request: Add an all rules preset

[electriquo]

While there is a recommended preset (flat and legacy), there is no preset for using all the rules.
This forces a manually configuration of all the rules, track manually rules addition/removal, and it makes eslint configuration longer than needed.

Could you please share why there is no all preset?
Would you consider adding one?

The plugin currently offers a recommended ruleset (both flat and legacy), which is helpful for most users. However, there is no equivalent preset that enables all available rules.

Why this matters

Without an all preset, users who want to:

• enable all rules for stricter linting or testing
• catch new rules as they're added/removed
• or simply avoid piecemeal configuration

must manually maintain a list of every rule. This increases maintenance overhead, especially when new rules are added or deprecated over time.

Request

• Could you share any reasons why an all preset hasn't been included so far?
• Would the team consider adding an all preset (similar to how some other ESLint plugins do)?

This would help users who want full rule coverage while still keeping configuration clean and up to date.

Thanks for your work on this plugin!

[ljharb]

That would be a bad idea, because it would turn adding a rule from semver-minor into semver-major.

[electriquo]

@ljharb Maybe we can explore alternative approaches that preserve backward compatibility while still achieving the desired behavior?

[ljharb]

Enabling all rules isn't inherently a good idea. In other words, the desired behavior - not having to make decisions - is actually an incorrect desire. You always should be manually monitoring rule and option additions in the eslint plugins you use. There's no way to avoid that, nor should there be.

[electriquo]

This forces a manually configuration of all the rules, track manually rules addition/removal, and it makes eslint configuration longer than needed.

@ljharb How would you advise to handle that?

[ljharb]

The same way everyone else always does - when you do an upgrade of eslint or any of your eslint plugins, and it's a minor or major bump, see what's changed.

Personally I use npx eslint-find-rules to see what rules i might be missing.

[OlivierZal]

Against an all config: some rules might conflict with others (default vs no default, etc.).

[electriquo]

I wonder why is this the case...
Is there any list of conflicting rules?

[OlivierZal]

Because some of these rules are kind of stylistics or depend of dev philosophy, so the developers can choose the behavior they want.