no compiler options

There are also a number of compiler options that are prefixed with the word "no". These options are similar to the "strict" options, in that they further guard our code against things like unused parameters, implicit returns, and implicit any. In this section of the chapter, we will take a look at these compiler options and how they can detect potential errors within our code. These parameters are similar in nature to "strict" parameters, in that they can be turned on or off and can be introduced into a code base gradually.

Note that if the "strict" compiler option has been set to true, then all of these options will be true as well.

noImplicitAny

When a type has not been specified for a property, parameter, or function return type, the TypeScript compiler will automatically assume that it is of type any. In strict mode, this will generate an error. Consider the following code:

declare function testImplicityAny...