唯然

It's required to return a value in fixers (to catch possible errors). if you don't want to fix in some cases, please use `return null;`

I can take it. 😄

the thoughts behind @eslint-community is *not* the eslint team to maintain these projects. It is to help the important projects being well-maintained. e.g. find maintainers.

Tried this option on my computer and it didn't output anything: ```sh ➜ eslint git:(pr17850) node ./bin/eslint.js --stats ./eslint.config.js (node:58409) ESLintIgnoreWarning: The ".eslintignore" file is no longer supported. Switch to...

as a start, I've made a repo: https://github.com/aladdin-add/eslint-gha-configs. I will try to: * Transfer it to eslint org, * Or create a new repo in eslint org and prepare a...

sure, PRs are welcome! 👍

I was able to repro! However, it's expected behavior: the required deps `eslint-plugin-react` does not allow eslint v9. So, package managers like npm will install v8 instead; while yarn v1...

I don't think it's appropriate (at least for most users) - eslint v9 is not supported by the plugin, and not even tested. We can output some information, the advanced...

some known issues: https://github.com/jsx-eslint/eslint-plugin-react/issues/3699

It doesn't seem reasonable to install a version that may not work. good to use `@eslint/backcompat` as described in https://github.com/eslint/rewrite/issues/4.