I have ESlint configured with vscode using the plugin, now I'm wondering is there some way I can stop ESlint from showing me the parser/syntax errors, so I can instead view the syntax errors that the Salsa language service provides by default.
Add a comment
|
9 Answers
Update: please refer this updated answer
Open up settings.json and add the property:
"eslint.enable": false
Check: https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint
5 Comments
Siraj Alam
is there any way to disable just few rules rather than the whole eslint?
Kushagra Sharma
@SirajAlam I don't think you can do that with VS Code settings, you would have to configure your .eslintrc file to disable specific rules. eslint.org/docs/user-guide/configuring
Muhammad Awais
this warning is shown This setting is deprecated. Disable ESLint using the extensions viewlet.
pt12lol
@AwaisNasir definately agree. Only melMass updated their answer stackoverflow.com/a/65268582/1906088 and it needs to be appreciated cause it's the only one up to date for this one at the moment.
Dvd Franco
You should read @suyashpatil 's answer in this topic, it might be useful!
The old:
"eslint.enable": false
Is deprecated, now you need to use the builtin VSCode mechanism for disabling extensions:
Comments
In order to disable ESLint only for a specific repo (instead of disabling it globally). Create .vscode folder in your project root and there create a settings.json then add the following config:
{
"eslint.enable": false
}
Maybe after this setting you should consider adding the .vscode/settings.json line to your .gitignore file too, but it is based on your dev team's preference.
}
Additionally if you'd like to ignore only some vendor/3PP .js files only then you should consider creating an .eslintignore file. Read more about this here.
go to File => Preferences => Settings
go to Extensions=>ESLint
Uncheck the EsLint:Enable
Comments
If you want to disable eslint errors in VSCode, Go to settings.json and disable all rules like this
"eslint.rules.customizations": [
{
"rule": "*",
"severity": "off"
}
]
This will disable all the eslint rules for you. If you want to disable a particular rule like "@typescript-eslint/no-this-alias", you can do the following
"eslint.rules.customizations": [
{
"rule": "@typescript-eslint/no-this-alias",
"severity": "off"
}
]
2 Comments
Frimlik
This is the correct answer in case user doesn't want to disable ESlint totally, but wants to keep ESlint formatting while saving file, for example.
btown
You can also use severity "warning" if your organization has a strict config that marks many things as errors, but you want them to show as yellow not red!
In VSCode, go to
File >> preferences >> settings
Type 'eslint quiet' in the search bar and click the check box for quiet mode.
In quiet mode, eslint would ignore basic errors. This should work for many VSCode users as at March 4, 2022. You're welcome!
1 Comment
Seth Falco
To be more precise, the Quiet setting ignores warnings in the VSC UI.
1-) npm install -g eslint
2-) Open up settings.json and add the property: "eslint.enable": false
Comments
Please open settings.json file and edit the configuration as below:
"eslint.enable": false
Hope this helps.
2 Comments
snoob dogg
@SethFalco Are you sure it fixes automatically the eslint errors ? I do not have that behavior on my side
Seth Falco
The answer has changed since I commented on it. The original version of this (see edit history) had an entirely different answer. I'll delete my comment to avoid confusion.
I don't understand why some answers states that eslint.enable is depracted. it works for me. in my WorkSpace settings (JSON), I add the following configuration and eslint errors disapears
{
...
"settings": {
"eslint.enable": false
},
}
