You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tsc command now has useful logging in case of success by default.
💻 Use Cases
Currently tsc doesn’t log anything about the project it’s checking. In case of success, it logs nothing. If a command run takes longer and emits nothing, I usually get suspicious something went wrong.
A more serious use case are project references. TypeScript checks referenced projects one by one. A program may fail type checking. If it does, TypeScript will log which files failed type checking. However, it is ambiguous of which program this file was a part. It may be part of multiple programs. It may succeed type checking for one program, but fail in another. I.e. maybe one program should have excluded it. Or maybe it should have added a missing lib, but which program?
All of this can be debugged using --traceResolution, but that info is very verbose and it takes a clean and second run
The text was updated successfully, but these errors were encountered:
tsc -b -v does this already and has pretty reasonable verbosity; does that suffice (if not, why) ?
[9:23:01 AM] Project 'compiler/tsconfig.json' is being forcibly rebuilt
[9:23:01 AM] Building project 'D:/github/TypeScript/src/compiler/tsconfig.json'...
[9:23:07 AM] Project 'deprecatedCompat/tsconfig.json' is being forcibly rebuilt
[9:23:07 AM] Building project 'D:/github/TypeScript/src/deprecatedCompat/tsconfig.json'...
[9:23:07 AM] Project 'jsTyping/tsconfig.json' is being forcibly rebuilt
[9:23:07 AM] Building project 'D:/github/TypeScript/src/jsTyping/tsconfig.json'...
[9:23:07 AM] Project 'services/tsconfig.json' is being forcibly rebuilt
[9:23:07 AM] Building project 'D:/github/TypeScript/src/services/tsconfig.json'...
[9:23:10 AM] Project 'typingsInstallerCore/tsconfig.json' is being forcibly rebuilt
[9:23:10 AM] Building project 'D:/github/TypeScript/src/typingsInstallerCore/tsconfig.json'...
[9:23:10 AM] Project 'server/tsconfig.json' is being forcibly rebuilt
[9:23:10 AM] Building project 'D:/github/TypeScript/src/server/tsconfig.json'...
[9:23:11 AM] Project 'harness/tsconfig.json' is being forcibly rebuilt
[9:23:11 AM] Building project 'D:/github/TypeScript/src/harness/tsconfig.json'...
[9:23:11 AM] Project 'testRunner/tsconfig.json' is being forcibly rebuilt
[9:23:11 AM] Building project 'D:/github/TypeScript/src/testRunner/tsconfig.json'...
[9:23:13 AM] Project 'tsc/tsconfig.json' is being forcibly rebuilt
[9:23:13 AM] Building project 'D:/github/TypeScript/src/tsc/tsconfig.json'...
[9:23:13 AM] Project 'typescript/tsconfig.json' is being forcibly rebuilt
[9:23:13 AM] Building project 'D:/github/TypeScript/src/typescript/tsconfig.json'...
[9:23:13 AM] Project 'tsserver/tsconfig.json' is being forcibly rebuilt
[9:23:13 AM] Building project 'D:/github/TypeScript/src/tsserver/tsconfig.json'...
[9:23:13 AM] Project 'typingsInstaller/tsconfig.json' is being forcibly rebuilt
[9:23:13 AM] Building project 'D:/github/TypeScript/src/typingsInstaller/tsconfig.json'...
[9:23:13 AM] Project 'watchGuard/tsconfig.json' is being forcibly rebuilt
[9:23:13 AM] Building project 'D:/github/TypeScript/src/watchGuard/tsconfig.json'...
🔍 Search Terms
log which program is being checked
✅ Viability Checklist
⭐ Suggestion
Log the project that is being checked. Also log something if all checks pass. E.g.:
📃 Motivating Example
The
tsc
command now has useful logging in case of success by default.💻 Use Cases
Currently
tsc
doesn’t log anything about the project it’s checking. In case of success, it logs nothing. If a command run takes longer and emits nothing, I usually get suspicious something went wrong.A more serious use case are project references. TypeScript checks referenced projects one by one. A program may fail type checking. If it does, TypeScript will log which files failed type checking. However, it is ambiguous of which program this file was a part. It may be part of multiple programs. It may succeed type checking for one program, but fail in another. I.e. maybe one program should have excluded it. Or maybe it should have added a missing
lib
, but which program?All of this can be debugged using
--traceResolution
, but that info is very verbose and it takes a clean and second runThe text was updated successfully, but these errors were encountered: