Open mozhuanzuojing opened 2 weeks ago
@mozhuanzuojing Looks like eslint config not applied, because default oxlint is warn
@mozhuanzuojing Looks like eslint config not applied, because default oxlint is warn
That being said, oxlint doesn't read the config file .eslintrc
correctly under WSL
It looks like your .eslintrc
is not in your root directory. You should either move it to your project's root, or configure the extension to look for a config file at page/.eslintrc
.
.eslintrc
It looks like your
.eslintrc
is not in your root directory. You should either move it to your project's root, or configure the extension to look for a config file atpage/.eslintrc
.
I see, the oxlint plugin doesn't support .eslintrc
of front-end projects in vscode workspace
It does, just not by default. Again, you'll need to edit the extension settings.
It does, just not by default. Again, you'll need to edit the extension settings.
Even if you configure "page/.eslintrc", it does not take effect.
Hmmm ok, I'll take a look in to that
Can you run oxlint
and send the result?
Can you run
oxlint
and send the result?
Yeah, you could see they are all warnings, also language server just uses page/.eslintrc
as configuration file
Yeah, you could see they are all warnings, also language server just uses
page/.eslintrc
as configuration file
if page/.eslintrc effect , it output red color.
Looks like related to workspace
reproduced that too, can't wait 0.10.0 release for test it against release
upd: still reproduced
0.10.2 - fixed and works correctly
@DonIsaac cc
Version 0.10.2 has a small problem
0.10.2 - fixed and works correctly
@DonIsaac cc
no, still not in effect
WSL2 env:
Version: 1.94.2 (system setup) Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427 Date: 2024-10-09T16:08:44.566Z Electron: 30.5.1 ElectronBuildId: 10262041 Chromium: 124.0.6367.243 Node.js: 20.16.0 V8: 12.4.254.20-electron.0 OS: Windows_NT x64 10.0.19045