Summary

In this chapter, we took a look at the various strict compiler options available within the TypeScript compiler. We started with an example of nested configuration, where a tsconfig.json file can reference another one as a base. We then discussed four strict options that check our code base for possible errors, by detecting null variables, properties that have not been initialized, parameter types when using bind, call, or apply, and strict function types. We then went through the no compiler options, which help us to identify variables that could be of type any, unused variables, implicit returns, switch case errors, and incorrect scoping of this.

It is best practice for any new TypeScript project to leave the default strict option set to true. This will ensure that all of the options we have discussed will always be on and will help to trap a large portion of possible errors within our code. The only time that we should really be modifying these options is if we are...