I'm currently using eslint.rules.customizations and I was quite disappointed to find out we can only override existing rules, but not add new ones if a project does not contain them.

I'm aware the purpose of customizations is to customize an existing rule, but it would be extremely helpful if I could define a set of default rules I always like to work with on every project and have them applied independently regardless or not if the project contains them. This would save me some time checking if they are already there, contributing towards minimal configuration.

Why I find this helpful

I was working on a Typescript project which lacked the rule to detect async functions not awaited. When I noticed the problem, I had already wasted time with unexpected results. Using IntelliJ with code inspections would have saved me some time because I would see the inspection warnings by default. These inspections help make sure you're never going to miss rules that you find strictly essential.

Of course, I could simply add the rule myself and continue working on it, the point is I'm not always going to detect it upfront and it might save me time.

I don't intend to propose adding them by default as that would create backward compatibility issues and possibly disturb the current users, but instead:

• either a new attribute, such as eslint.rules.extend
• or a new attribute in each eslint.rules.customizations rule object.