he/him 
They are, unfortunately, really that bad most of the time.
Am I doing something wrong or are TypeScript errors actually this bad? Everything is on a single line. No highlighting. Entire types are exploded rather than only showing the relevant types.pic.twitter.com/Y0iFuhMRuA
-
-
- 4 more replies
New conversation -
-
-
Thank you so much!
End of conversation
New conversation -
-
As long as a program is completely type safe, does it really matter if it has no useful behavior?
-
TypeScript isn't type-safe by design, though o.O https://www.typescriptlang.org/docs/handbook/type-compatibility.html#a-note-on-soundness …
- 3 more replies
New conversation -
-
-
That's vs code. tsc normally prints them with a much nicer format
-
It has some newlines and indentation but it's still pretty bad
- 1 more reply
New conversation -
-
-
I think using `interface MyInterface` instead of `type MyInterface = {...}` should provide some better type errors in that case.
-
It is an interface from @types/node sadly
- 1 more reply
New conversation -
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.