Allow implicit any only for definition files

Tom Fenech picture Tom Fenech · Jul 29, 2016 · Viewed 11.7k times · Source

I am using TypeScript with the "noImplicitAny": true option set in my tsconfig.json.

I am using typings to manage type definition files and am including them using a reference path directive in the entry point of my app:

/// <reference path="./typings/index.d.ts" />

The problem is that some of the definition files rely on implicit any, so now I get a lot of compile errors from .d.ts files.

Is there a way to disable/silence these errors, for example based on the path or the file type?

Answer

cartant picture cartant · Oct 7, 2016

With the release of TypeScript 2.0, the skipLibCheck compiler option was introduced and it should solve your problem:

TypeScript 2.0 adds a new --skipLibCheck compiler option that causes type checking of declaration files (files with extension .d.ts) to be skipped. When a program includes large declaration files, the compiler spends a lot of time type checking declarations that are already known to not contain errors, and compile times may be significantly shortened by skipping declaration file type checks.

Since declarations in one file can affect type checking in other files, some errors may not be detected when --skipLibCheck is specified. For example, if a non-declaration file augments a type declared in a declaration file, errors may result that are only reported when the declaration file is checked. However, in practice such situations are rare.

It defaults to false and can be enabled in your tsconfig.json:

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