[Feature Request:] add support for config file name => eslint.config.js

Hi,

Configuration name *.config.js seems to be the most default/common value for most of majors libraries:

• webpack.config.js
• babel.config.js
• stylelint.config.js
• postcss.config.js
• prettier.config.js
• vue.config.js
• nuxt.config.js
• tailwind.config.js
• jest.config.js

I see only too libraries that doesn’t support this format:

• Eslint
• Browserlist (Browserlist issues 380)

It could be nice for Eslint to offer this option.

Following this convention will definitively help users. Having a consistent way to configure libraries would be easier and cleaner.

Just my two cents to make our life a little easier 😄 !

Cheers!

[eslint-deprecated[bot]]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to reach accepted status after 21 days tend to never be accepted, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.

[jimblue]

@kaicataldo, from Babel team:

We recommend to use the babel.config.js format. Babel itself is using it. (ref here)

It’s only two libraries from getting a new standard… could be worst! 😅 Using *.config.js as a convention will definitively help a lot… don’t you think?