Tooling for TypeScripts
TypeScript tooling covers the compiler configuration and surrounding build tools. The tsconfig.json file sets the target, module system, strictness and include paths, and the strict flag turns on checks such as strictNullChecks. Teams pair tsc with bundlers, ESLint with typescript-eslint and a formatter so type errors and style issues show up in the editor and in CI.
Stage: Project Setup · Part of the TypeScript roadmap · Last reviewed 19 November 2026
What to learn in Tooling
- Create a tsconfig.json with sensible target, module and strict settings
- Explain what strictNullChecks and noImplicitAny catch
- Run the compiler in watch mode and read its error messages
- Set up ESLint with typescript-eslint for a project
- Choose a build setup using tsc, a bundler or a runtime that strips types
Tooling interview questions
What does the strict option in tsconfig enable?
The strict flag turns on a family of checks, including strictNullChecks, noImplicitAny, strictFunctionTypes and others, making the compiler catch many more errors. New projects should enable it, and existing ones can adopt the individual flags gradually.
Does TypeScript check types at runtime?
No. Types are erased when compiled to JavaScript, so nothing checks them while the program runs. Data from outside, such as JSON from an API, must be validated at runtime with a library like Zod or custom checks if its shape matters.
Where Tooling fits in the TypeScript roadmap
Tooling belongs to the Project Setup stage (intermediate level), which takes about 17 hours. Compile and configure.
Other units in this stage
Back to the full TypeScript roadmap