ESLint version

v9.0.0-alpha.0

What problem do you want to solve?

Currently the configuration files for ESLint have to be placed in the root of the project (as described in the docs here).

Due to a lack of standards for where tools store their configuration, the number of top-level configuration files in projects is increasing day by day. See .config dir proposal for more context.

What do you think is the correct solution?

I propose supporting .config/eslint.js, .config/eslint.mjs and .config/eslint.cjs as alternative places to check and load the configuration if the top-level eslint.config.js/mjs/cjsdoes not exist to unblock adopting this new convention across the ecosystem.

While it can take a while to onboard more tools with this new convention, it will be an egg-and-chicken problem to adopt a new convention like this unless more mainstream tools onboard to support it.

Participation

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

Additional comments

See what tools already support this convention here.