Panic `crates\oxc_linter\src\config\config_store.rs:184:22`

[Hideman42]

With version 1.9.0 on win64

thread '<unnamed>' panicked at crates\oxc_linter\src\config\config_store.rs:184:22:
called `Result::unwrap()` on an `Err` value: PluginNotFound { plugin: "eslint-plugin-import" }

 0:     0x7ff72e2275df - <unknown>
 1:     0x7ff72dd3c79b - <unknown>
 2:     0x7ff72e226af4 - <unknown>
 3:     0x7ff72e227414 - <unknown>
 4:     0x7ff72e226760 - <unknown>
 5:     0x7ff72e23a089 - <unknown>
 6:     0x7ff72e239fdf - <unknown>
 7:     0x7ff72e23ab6e - <unknown>
 8:     0x7ff72e269111 - <unknown>
 9:     0x7ff72e269670 - <unknown>
10:     0x7ff72deba722 - <unknown>
11:     0x7ff72deaf763 - <unknown>
12:     0x7ff72de80a77 - <unknown>
13:     0x7ff72e2a7053 - <unknown>
14:     0x7ff72e184d52 - <unknown>
15:     0x7ff72e186ac8 - <unknown>
16:     0x7ff72e237bfd - <unknown>
17:     0x7ffd2caee8d7 - BaseThreadInitThunk
18:     0x7ffd2e8bc34c - RtlUserThreadStart

[Hideman42]

Okey, after reading the source, the panic is due when the rules is not found.
When updating to latest 1.9.0 some rules as been moved (for instance from eslint/rule to import/rule) therefore my config file was the cause of the issue.
Would be nice to at least log the rule that is not found for easier debugging.
For solving my issue I had to run the extract and make a custom script to find my rules in that extract 😕

[camc314]

Yeah, we will have a much nicer error in the next release.

The simple solution is that somewhere in your overrides, you specify "eslint-plugin-import" plugin. Instead, change it to "import" and the panic should disappear

[camc314]

fixed by #12502