Eslint plugin (eslint v9) can't find Typescript config file (eslint.config.ts)
I have a small project where I use Eslint v9 (9.14 as of writing) and an `eslint.config.ts` config file. As per the Eslint instrictions, I have also installed `jiti` (Configuration Files - ESLint - Pluggable JavaScript Linter). And in my IDE Eslint config I have added the “Extra eslint options” `--flag unstable_ts_config` (ESLint | WebStorm Documentation).
However the IDE Eslint plugin still refuses to work, saying it can't find the config file:

If in the IDE settings I also manually specify the Eslint binary and the config file, I get a new error implying that the imports within the config file aren't working correctly (but `jiti` is being used now, good?):





All this is odd because I have no problems with:
1. Running `npx eslint --flag unstable_ts_config .` in the CLI for this project.
2. Using VSCode and the main Eslint extension for it, with the same `--flag` added as extra arguments.
So it is just a Webstorm Eslint plugin issue as far as I can tell.
I am on latest Webstorm v2024.3. I use Windows 11 with WSL v2 (NixOS).
Please sign in to leave a comment.
Unfortunately I failed to reproduce the issue in Webstorm v2024.3 using similar setup.
What package manager do you use? Would it be possible to narrow the problem down to a minimal repo project and share this with us?
Share how? I have one.
You can share the project via https://uploads.jetbrains.com/ form and let me know the upload ID.
Thank you.
Here it is.
Upload id: 2025_03_12_2BZdzr7M9puq8cii1N2Fma (file: idea-eslint-repro.zip)
Unfortunately I failed to reproduce the issue in the project you have shared:
Which version of the IDE are you using?
OP here, sorry I left this after your initial response Elena Pogorelova. I figured out later that this issue only ocurred on Windows 11 when Webstorm had opened a repo that was within a WSL2 filesystem. Opening a repo on the windows filesystem did not have any issue. Booting a complete linux OS (tested Debian) did not have the issue either.
Thanks Elena, I was on an older version that pre-dated flatConfig as you suspected. Upgraded and it's working correctly now.