exhaustive-deps not checked by either tool

[FMP1783]

I found that react-hooks/exhaustive-deps is not being checked when using plugin:oxlint/recommended.

This rule is in correctnessRules, so ESLint disables it. But oxlint doesn't enable it by default either.

I think this contradicts what was said in #385 - rules not enabled in oxlint shouldn't be disabled in ESLint.

Is this intentional?

Environment

• ESLint: 8.57.1
• eslint-plugin-oxlint: 1.26.0
• oxlint: 1.26.0
• Config: .eslintrc with extends: ["plugin:oxlint/recommended"]

[Sysix]

rules not enabled in oxlint shouldn't be disabled in ESLint. Is this intentional?

In the linked issue, the problem is talking about buildFromOxlintConfig(File).
Using oxlint/recommended is the same as oxlint/correctness.
It will disable all categories.correctness rules, even if you are not using them inside oxlint.

Maybe try @oxlint/migrate --merge to add missing rules inside your oxlint config :)

[s-horiuchi1101]

I tried @oxlint/migrate, but it showed "could not autodetect eslint config file".
Our project uses the .eslintrc format. Does this tool only support ESLint v9 flat config?

[Sysix]

Does this tool only support ESLint v9 flat config?

Yes, only the flat config, but this is available with v8 too.
And you can use this script to https://github.com/eslint/eslintrc to create a migration step between the two configs.

Hope this helps 🤞

[FMP1783]

I was able to successfully migrate using @oxlint/migrate.

on ESLint 8

You mentioned that flat config is available with ESLint 8 too. However, when I tried to use flat config with ESLint 8, I got this error:

Error: Cannot find package 'eslint/config'

What I Did

1. Upgraded to ESLint 9
2. Used @eslint/migrate-config to convert .eslintrc to eslint.config.mjs (it uses FlatCompat to load legacy plugins)
3. Removed plugin:oxlint/recommended from the config
4. Ran npx @oxlint/migrate eslint.config.mjs
5. Added plugin:oxlint/recommended back

At first I ran @oxlint/migrate with plugin:oxlint/recommended still in the config, which caused exhaustive-deps to be output as off in
.oxlintrc.json. After removing it before running migrate, exhaustive-deps was correctly set to warn.

Now oxlint checks exhaustive-deps and ESLint skips it.

I'll consider adopting ESLint 9. Thanks @Sysix!