-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
When using ESLint and TypeScript checkers together, ESLint checker only runs at startup #373
Comments
What's the version of typescript and eslint in your project? |
Hey, thanks for taking a look at my issue! I'm on This is the project in which I'm experiencing the symptoms (on the |
same for me for a year |
I had the same issue (eslint run only once at startup) but apparently not for the same reason, I just mention it if it can help someone: |
This plugin reads the file path from the command and sends it to the watcher for monitoring. Therefore, if no file path is provided, no files will be monitored. As a result, even when using Flat Config, a path must be passed for it to function properly. |
I did pass the current directory |
Sorry, I didn't notice that you provided |
Describe the bug
When I start up my Vite dev server, ESLint and TypeScript both run.
When I change a file after this point, only TypeScript runs. It runs twice on each file change. My logs look like this:
Reproduction
My config:
I believe this is all that's needed to reproduce the behavior!
Expected behavior
ESLint and Typescript checkers run once each on every change
System Info
System: OS: Linux 6.8 Debian GNU/Linux 12 (bookworm) 12 (bookworm) CPU: (16) x64 AMD Ryzen 7 5800X3D 8-Core Processor Memory: 12.98 GB / 31.26 GB Container: Yes Shell: 5.2.15 - /bin/bash Binaries: Node: 22.4.1 - /usr/local/bin/node Yarn: 1.22.22 - /usr/local/bin/yarn npm: 10.8.1 - /usr/local/bin/npm npmPackages: vite-plugin-checker: ^0.7.2 => 0.7.2
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: