Exclude node_modules from "problems"

Question

I'm running this task:

{
        "taskName": "tsc watch",
        "command": "tsc -w",
        "type": "shell",
        "problemMatcher": "$tsc-watch"
}

with this tsconfig:

{
    "compileOnSave": true,
    "files": [
        "src/index.ts"
    ],
    "compilerOptions": {
        "module": "commonjs",
        "sourceMap": true,
        "outDir": "dist/"
    },
    "exclude": [
        "node_modules"
    ]
}

the file index.ts only has one line in it:

console.log('Is it working?');

And the "problems" tab is filled with HTML related warnings from random npm modules. Why? And how do i stop it?

Edit1:
I managed to find a hack that works, by excluding the node_modules folder from the explorer:

/* settings.json */
{
    "files.exclude": {
        "**/node_modules": true
    }
}

However this is a hack, and i still want a proper answer..

Gene

Exclude option does not have any effect if it is used by your source code. Since it is still not excluded, you wish to suppress checking for third-party libraries. It is where the accepted anwser regarding the "skipLibCheck" option shines. – Whoremaster

Answer 1

I stumbled upon this issue as well. The only solution I found was add the skipLibCheck option and set it to true in the compilerOptions of my tsconfig.json:

{
    "compilerOptions": {
        "skipLibCheck": true
    }
}

According to the doc, it will skip type checking of all declaration files (*.d.ts), which were the ones throwing the warnings in my case.

Judicious

mmm not working for me :( – Warrantee

maybe restart the service again. That helped me right after skiping the lib check – Capitulate

Answer 2

All you should need is a tsconfig.json with:

{
    "compilerOptions": {
        "skipLibCheck": true,
    }
}

Marxist

This adds absolutely nothing to the accepted answer – Sorbian

Hmmm, I just realized that your answer was the better one before the last edit of the accepted answer. Sorry. – Sorbian

and again, this doesn't work for me either. – Overstrain

The edits on the accepted answer is really, REALLY bad for this answer. I downvoted this answer because it was copying the accepted answer, then realised the accepted answer is copying this answer. – Incalescent

pretty classic StackOverflow in action :) – Marxist

Answer 3

I have found another "cheat" for making that problem disappear after I tried everything and nothing worked. I added at the end of the file:

export {}

This somehow worked. I am not happy with that solution but that's the only thing that worked for me.

Antheridium

Where would you place this? The question is about excluding all errors originating from node_modules. – Incalescent