he/him 
Why run twice "tsc --noEmit" ?
Wrote this script to run a full TS check and then open all files with errors in VSCode. Shocked more people don't complain about this.https://gist.github.com/sebmck/bbf4fa4ab7b4814b1a1e56a4f5f85e80 …
-
-
-
Different TTY and non-TTY output
End of conversation
New conversation -
-
-
I guess because tsc is built into my editor and the invalid files get shown in the sidebar, iirc.
-
Only if you've opened them when they've had errors. AFAIK files wont be updated in the sidebar, and fixed errors wont go away in the sidebar either until you've opened the file.
- 1 more reply
New conversation -
-
-
Not a TS user myself; when you say shocked more people don't complain about this, what specifically are you referring to?
-
You can edit a file in VSCode that could introduce errors in other files. The only way to find them is to either run tsc --noEmit` manually or open that file in your editor (how are you meant to know what file?). Errors are only displayed in the files you have open.
- 2 more replies
New conversation -
-
-
We do, but it’s a stalemate between the vscode team and the ts team. It seems ts server doesn’t support something vscode needs for it. Shocking that of all things Flow does report errors on vscode’s explore sidebar (with an extension).
- 3 more replies
New conversation -
-
-
Coming from a Java background, this has been the single most disturbing thing I had to adjust to. webpack / whichever CLI will catch and report these errors, but you can’t trust the IDE.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Yea, I found this really annoying when doing the initial mass conversion into TS. After that it’s kinda meh.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.