-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terse mode output from tsc --build
#25562
Comments
Is this the same as #25286? If so, please feel free to close that one. |
The node CLI convention for long-running CLI feedback (I'm thinking of In the watch case, it could add then remove the In any case, this seems the about the right level of output. As a bikeshed, I prefer the "Building" lines to be more regular so it's easier to scan, e.g. (if I'm reading the example right):
|
I would LOVE this flag. I currently have a build process where I transpile a TS library with Babel showing an output of each file being build / moved. I then use tsc to generate the *.d.ts files for consumption in other packages. I would be awesome to see each output file being built and moved similar to how Babel shows. EDIT: I actually found that |
Its been two and half year since the last comment. Any updates? |
Search Terms
tsc --build mode console logging output verbose
Suggestion
Have a middle-ground between
verbose
and "nothing" when runningtsc -b
Use Cases
Initial feedback was that "
tsc -b
should print nothing by default (if there are no errors)", which is a reasonable first principle to work from. However, it's nice to have some rough idea of what's going on, especially because atsc -b
invocation might take quite a while, depending on what's up to date.Users today can get more output by running with
--verbose
, which prints some fairly detailed spew:The
verbose
output was written primarily as an "Explain why something is happening"; there is no in-between setting that says simply "Explain what is happening".This is compounded under
--watch
wheretsc -b
prints errors, but doesn't print "No errors", so you can't really know if your compilation succeeded or if tsc simply missed a file change.Proposal
--terse
strikes a middle ground between the default (silent) andverbose
. Its short name would be-t
which doesn't conflict with anything I can think of adding in the near term.Examples
Checklist
My suggestion meets these guidelines:
The text was updated successfully, but these errors were encountered: