Support `tsc --build --noEmit`

Suggestion

🔍 Search Terms

tsc --build --noEmit
build noEmit

List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Allow tsc --build --noEmit, the relevant types can be emitted to the tsbuildinfo for incremental building. This is very useful to allow type checking only for projects using project references and working with a bundler. e.g. A create-vue project, which currently has to resort to hackery such as vue-tsc --noEmit -p tsconfig.vitest.json --composite false which is not as accurate as type checking each project individually.

📃 Motivating Example

tsc --build --noEmit is now supported, allowing to only run type checking for projects using project references that don't also build types using tsc.

💻 Use Cases

Type checking only, for projects using other build tools than tsc but still using project references for each of configuration.

Beginne damit, die bestehende Behandlung von tsc --build für Projektreferenzen und die inkrementelle Generierung von tsbuildinfo zu untersuchen; das Issue nennt keine spezifischen Dateien oder Tests. Als abgeschlossen gilt die Arbeit, wenn tsc --build --noEmit eine Typprüfung ohne Ausgabe von Typen durchführt und dabei die relevanten Informationen für inkrementelle Builds aufzeichnet.