How to find/debug what file(s) included given file during typescript compilation

Search Terms

find why was file included during typescript build

Suggestion

Be able to find out why a file was checked by TS compiler during a build.

Use Cases

Sometimes testing files gets somehow mixed into the type checking for dev/prod builds.

Examples

If a flag explain-inclusion=FLFolder.mock.ts is present:

projects/folder-listing/src/app/services/FLEntities/FLFolder.mock.ts was included, because it was requested by:

• projects/folder-listing/src/app/services/FLEntities/FLFolder.ts at (3:26)
• projects/folder-listing/src/app/services/main.service.ts (7:10)
  ... (Only first level, the developer should repeat the process as needed)

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.

L’issue ne nomme pas les fichiers d’implémentation, les tests ni les points d’entrée du compilateur. Commencez par retracer la manière dont TypeScript détermine l’inclusion des fichiers et la manière dont les diagnostics existants de la ligne de commande sont exposés. C’est terminé lorsqu’il existe un moyen documenté ou testé d’identifier pourquoi un fichier a été inclus, y compris le fichier à l’origine de la demande et l’emplacement dans le code source décrit dans l’exemple.