Use typescript compiler parameter 'skiplibcheck' - usage of the typescript compiler argument'skiplibcheck'

problem ：

I've been researching around for a further explanation into the skipLibCheck TypeScript compiler argument to determine the safety of having this set to true . I've been studying skipLibCheck TypeScript Further explanation of compiler parameters , To make sure it is set to true The security of .The most in-depth explanation I found is the following: The most profound explanation I have found is as follows ：

New --skipLibCheck TypeScript 2.0 adds a new --skipLibCheck compiler option that causes type checking of declaration files (files with extension .d.ts) to be skipped. new --skipLibCheck TypeScript 2.0 Added a new --skipLibCheck Compiler Options , This option causes the declaration file to be skipped （ extension .d.ts The file of ） Type check of .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. When a program contains a large declaration file , The compiler spends a lot of time type checking declarations that are known to contain no errors , And by skipping the declaration file type check, compilation time can be significantly reduced .

Since declarations in one file can affect type checking in other files, some errors may not be detected when --skipLibCheck is specified. Because the declaration in one file will affect the type checking in other files , Therefore, in the specified --skipLibCheck Some errors may not be detected when .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. for example , If the undeclared file extends the type declared in the declaration file , May result in errors reported only when checking the declaration file .However, in practice such situations are rare. However , In practice , This is a rare case .

I understand that you obviously get a performance benefit from the compiler not having to type check files which are considered not to contain errors but I've seen this flag being used to get around errors being emitted from the compiler in relation to the declaration files having problems. I know you can obviously get a performance advantage from the compiler , Instead of typing a check file that is considered to contain no errors , But I have seen that this flag is used to solve the problem of errors related to the declaration file issued by the compiler .

Surely using this flag to get around this decreases the integrity of the typing of your application? Using this flag to solve this problem will certainly reduce the integrity of the application type ？

---

Solution ：

Reference resources ： https://stackoom.com/en/question/3XUgN