Disable TSLint in VSCode

Question

So this feels like this should be such an easy task but it's starting to drive me insane. I can't seem to turn off TSLint or TS or whatever it is that gives me these errors. I just want the ESLint with my own configured rules, nothing else.

Is it built in TS? I have disabled TSLint extension (even uninstalled it). I have set the following rules:

"typescript.format.enable": false,
"typescript.validate.enable": false,

Still gives me error. How do I turn this off?

Answer 1

It seems that the error is coming from the TypeScript extension, which is also handling the JavaScript IntelliSense. Due to some UX ignorance, VSCode prefixes the error with [ts] instead of [js].

To disable these validations, set

"javascript.validate.enable": false

See this issue for more details.

Answer 2

I've been hunting around for this answer for the better part of a month now. I found a solution that works in VS Code that isn't a wholesale disabling of all validation for javascript and also did not require that I add files/declarations to a repository that is not mine.

Add this line to your user settings:

"javascript.suggestionActions.enabled": false

Unlike "javascript.validate.enable": false (which you should not use), the above setting will remove those annoying [ts] Could not find a declaration file for module errors for untyped module imports in javascript files and it will still play nice with linters and give you appropriate and relevant errors.

Answer 3

Ctrl-Shift-P (Command Palette)

Type Preferences: Open Workspace Settings JSON

add

"tslint.enable":false

Or

"typescript.validate.enable": false

But beware, as @rawpower has said "We don't want to disable errors, just 'warnings'"

Anyways, save and restart VSCode

Answer 4

Most of the answers turn off the duplicate errors for JavaScript, not TypeScript, like the OP asked about. What worked for me was:

1. Uninstall the TSLint vscode extension
2. Install the ESLint vscode extension
3. Finish configuring ESLint for TypeScript (will now have both "ts errors" and "eslint errors" at this point like the OP).
4. Open settings.json and add this to the bottom: "typescript.validate.enable": false

At first, I was concerned that this option would turn off all typescript validation, including eslint, but fortunately that wasn't the case. It only disables the built-in vscode typescript validation and leaves eslint alone.

The most important part is adding "typescript.validate.enable": false to settings.json

Or, instead of manually editing settings.json, another way is to uncheck the box in the settings menu (ctrl+'):

FYI, you can add it to either your User settings.json (applies to all your projects) or your Workspace settings.json (only applies to the current project).

Answer 5

Just open settings (File -> preference -> Settings) or short cut (Ctl + ,) and search for the 'Javascript Validate'.

Answer 6

As far as I understand, VSCode is checking himself the javascript, and believe the TypeScript errors are what you expect.

To stop VSCode from checking my code, and let only the eslint extension check it, I did:

• use eslint to check my javascript (install the extension)
• tell vscode not to check my javascript files: in jsconfig.json:

{
   "compilerOptions": {
      "checkJs": false
   }
}

I still see the "eslint" reported errors, and those errors are coherent with command line run of eslint.

PS: jsconfig reference here: https://code.visualstudio.com/docs/languages/jsconfig

Answer 7

For me the solution was to create a jsconfig.json file at root level. Inside you can configure the compilerOptions, which did the trick for me after restart of VSCode.

Answer 8

In VSCode User settings.json, I changed js/ts.implicitProjectConfig.checkJs from true to false

// settings.json
{
    "js/ts.implicitProjectConfig.checkJs": false
}