question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Suggestion: tsc should display a one line summary

See original GitHub issue

Suggestion: tsc currently list the errors. Sometimes you want to see if the number of errors increases or decreases.

Proposition:

$ tsc
FooBar.tsx(66,59): error TS2339: Property 'query' does not exist on type 'Location'.
Hello.tsx(42,60): error TS2339: Property 'query' does not exist on type 'Location'.
dispatcher.ts(1,13): error TS6133: '_' is declared but never used.
World.test.ts(3,35): error TS7006: Parameter 'reason' implicitly has an 'any' type.
World.test.ts(3,43): error TS7006: Parameter 'promise' implicitly has an 'any' type.
World.test.ts(18,13): error TS6133: 'hello' is declared but never used.
mock.ts(194,23): error TS6133: 'ruleId' is declared but never used.
mock.ts(221,8): error TS2339: Property 'fetch' does not exist on type 'Window'.

Compilation done in 2.6s - 8 errors
$ tsc
[...]
Compilation aborted [...]

Could be the opportunity to display other informations (compilation time for example) given that it fits in a single line (72 columns).

(I’m not talking about --diagnostics)

Issue Analytics

  • State:open
  • Created 7 years ago
  • Reactions:10
  • Comments:10 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
ashfurrowcommented, Oct 28, 2018

I have just opened a pull request to implement this: https://github.com/Microsoft/TypeScript/pull/28196

1reaction
gcnewcommented, Feb 21, 2017

No, please! This would actually make the compiler harder to use from command line scripts. The other major compilers don’t work this way either.

Edit: maybe it is appropriate for --pretty, but I think the clean and easily parsable default output should stay unchanged.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Writing a One-Sentence Summary - Rachelle Gardner
Tips: → Keep it simple. One plotline, 1 or 2 characters. → Use the strongest nouns, verbs and adjectives.
Read more >
TypeScript Programming with Visual Studio Code
You can click on the summary or press Ctrl+Shift+M to display the PROBLEMS panel with a list of all current errors. If you...
Read more >
Use tsconfig.json for tsc with syntastic in vim - Stack Overflow
I already have tsc activated in vim . Any suggestions for how I could get tsc to use the closest parent's tsconfig.json file...
Read more >
JSDoc Reference - TypeScript: Documentation
@param allows a similar syntax for one-off type specifications. Note that the nested property names must be prefixed with the name of the...
Read more >
TypeScript | WebStorm Documentation - JetBrains
View description of an error in the editor. Apply the suggested quick-fix or click More actions and select the relevant one from the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found