ESLint version

HEAD

What problem do you want to solve?

We inherited a lot of hardcoded rule configuration types from @types/eslint, but these were all handcoded and we've already seen that they are out of date. (#18902, #18906, #18905, #18903, #18901). Keeping the types in sync with rules is going to be a problem going forward.

What do you think is the correct solution?

We should create a script that automatically generates the rule config types based on the rule schemas.

Participation

• I am willing to submit a pull request for this change.

Additional comments

Looking for a volunteer for this.