Typescript throws errors in node_modules with strict compiler options

Question

There are several github issues about why errors in node_modules are thrown although that folder is excluded in tsconfig.json. If there is any import on the lib it is included, ignoring the exclude property.

However when using stricter compiler options (i.e. strictNullChecks, noUnusedLocals, ...) and reference any lib that is not designed to work on those options, errors are thrown.

Thus whenever using such a lib it is always a decision of not using the lib or not using the compiler option. However there are big libraries/frameworks that do not support those options (i.e. Angular) so it seems like there is no way of using those options to ensure strict checks in the own project.

Am I missing some possibility to avoid errors in node_modules being thrown? If not, is there any technical requirement to apply those rules to all imported libraries or what is the reasoning behind this behaviour?

lesyk · Accepted Answer · 2017-11-16 09:24:18Z

1

In all my projects setup I have structure where in root I have:

Folders:

code_folder
node_modules

Files:

package.json
README.md
tsconfig.json
tslint.json
yarn.lock

Then in tsconfig.json:

{
    "compilerOptions": {
        "lib": ["es6"]
    },
    "include": [
        "code_folder/*"
    ]
}

answered Nov 16, 2017 at 9:24

lesyk

4,1473 gold badges28 silver badges40 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Typescript throws errors in node_modules with strict compiler options

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related