noEmit and emit Options

noEmit turns TypeScript into a checker without producing JavaScript. This is useful when another tool performs bundling or transpilation. Emit-related options such as declaration and sourceMap control specific artifacts when emission is enabled; neither type checking nor noEmit executes your application.

The compiler can check the assignment whether or not JavaScript is emitted. With noEmit:false, ordinary tsc writes JavaScript; with noEmit:true, it writes no files.

noEmit:true will not start your application or write fresh JS. Use a separate runtime/bundler step when necessary.

Save as noemit-emit-options.ts. The following program passed strict TypeScript compilation, and the displayed output was captured by executing its emitted JavaScript with Node.js 22.16.0.

TypeScript source

const count: number = 3;
console.log(`Count: ${count}`);

Verified output

Count: 3

Compile: npx tsc --strict --target es2022 --module commonjs noemit-emit-options.ts; run: node noemit-emit-options.js. For Node.js API examples, install @types/node first. For browser projects, use the browser-specific instructions below.

The example demonstrates the code-level behavior; the related configuration or test commands are shown separately when needed.

The compiler can check the assignment whether or not JavaScript is emitted. With noEmit:false, ordinary tsc writes JavaScript; with noEmit:true, it writes no files.

Predict what changes if you alter one input. Then run the code to compare your reasoning with the real output.

Practical project lab: These are real configuration and source-file examples, not a TypeScript object that merely describes settings. Place the files at the named paths relative to one project directory.

tsconfig.json

{"compilerOptions":{"target":"ES2022","strict":true,"noEmit":true}}

main.ts

const total: number = 7; console.log(total);

Commands

npx tsc --noEmit -p .

No JavaScript is emitted. Disable noEmit before attempting to run generated JavaScript.

This local compiler or test-runner mini-project was validated in addition to the primary program.

noEmit:true will not start your application or write fresh JS. Use a separate runtime/bundler step when necessary.

Identify whether the failure is a type-checking issue, a configuration issue, or a runtime behavior issue before choosing a fix.

Run tsc with --noEmit, verify no output file is created, then build without it and compare.

Write down your expected result first. For configuration examples, compare compiler output and diagnostics; for test examples, make the assertion fail deliberately to verify that the tool reports it.

For the exact current options and platform behavior, consult the official documentation. These examples were verified using the tool versions described above.

noEmit turns TypeScript into a checker without producing JavaScript.

Run the primary example, then complete the practice task or environment-specific lab.