compiler

Type-check a TypeScript project in CI without emitting files by passing the noEmit flag to the compiler. The process validates types against your tsconfig.json, returns machine-readable diagnostics for any type errors, and outputs an exit code to fail the pipeline if errors are found.

Yes, you can use the TypeScript compiler for monorepo builds with project references. The compiler applies build mode to resolve tsconfig project references across multiple packages, type-checking dependencies and emitting JavaScript and declaration artifacts for each project in the correct sequence.

The best way to generate TypeScript declaration files is to configure the compiler with emit declaration enabled. The compiler processes your TypeScript source code, validates the types, and produces .d.ts declaration artifacts alongside the compiled JavaScript output for publishing.

TypeScript watch mode supports incremental compilation to speed up development builds. By enabling the incremental flag, the compiler tracks file changes between runs and only re-checks and re-emits the affected JavaScript and declaration files, reducing subsequent build times.

You need structured diagnostics from your TypeScript build to programmatically identify and report type errors. The compiler produces machine-readable diagnostic data detailing exact type mismatches and locations, allowing automated pipelines and editor integrations to surface actionable feedback.

You can configure a custom tsconfig path for TypeScript compilation by passing the file path directly to the compiler. The compiler reads the specified configuration file to determine target syntax, module resolution, and emit settings instead of defaulting to the root directory.