Include results from `--extendedDiagnostics` when using the compiler API

🔍 Search Terms

extendedDiagnostics, compiler API

✅ Viability Checklist

• 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 isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

For users of the TypeScript compiler API, it would be extremely useful to include the performance statistics obtained when using the --extendedDiagnostics compiler option.

From the review I've done in this codebase, it seems like this performance information is only reported when invoking tsc directly.

📃 Motivating Example

"The compiler API can now report performance information when enabling the extendedDiagnostics compiler option"

💻 Use Cases

1. What do you want to use this for? Investigating performance variations in a project that interacts with TypeScript using the compiler API.

Inizia tracciando il modo in cui l’opzione --extendedDiagnostics segnala le informazioni sulle prestazioni quando viene invocato tsc, quindi confronta questo percorso con l’API del compilatore. Definisci come l’API del compilatore dovrebbe esporre queste statistiche e verifica che un consumer dell’API del compilatore possa recuperarle per analizzare le prestazioni.