Support multi-threaded compilation for --build

Search Terms

Project references, multi-thread, compilation, performance

Suggestion

We have migrated our main project to use project references. It simplifies the development workflow, but brings basically 0 noticeable performance improvement (for both local development and CI). There's even an illusion that now we get worse performance during development.

I guess the main reason behind this is lacking support for multi-thread compilation.

Use Cases

Improve compilation performance.

Examples

N/A

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, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

El issue menciona el flujo de trabajo de --build, pero no identifica archivos, pruebas ni un punto de entrada para la implementación. Empieza por localizar la ruta de compilación de --build y revisar cómo se compilan las referencias de proyecto. Se considerará terminado cuando la compilación multihilo mejore el rendimiento sin cambiar el JavaScript generado ni el comportamiento existente en tiempo de ejecución.