search

microsoft / typescript-analyze-trace

A tool for analyzing the output of `tsc --generateTrace`
MIT License
309 stars 15 forks source link

Feature: Support language service traces #16

Open amcasey opened 2 years ago

amcasey commented 2 years ago
  1. There won't be types
  2. Events (e.g. program construction) are repeated so aggregation will be required
  3. Command information is present
danvk commented 2 years ago

+💯 to this! I have no major complaints about TypeScript's batch compile time (tsc) but find the latency in autocomplete and error checking in my editor quite irksome. I'd love some tooling to help track down this kind of performance, which is much harder to measure.

amcasey commented 2 years ago

@danvk Step one is to manually review some editor traces - any chance you'd like to share yours? Fair warning: it will contain the paths of all your files and imports.

danvk commented 2 years ago

@amcasey I can't share traces in a public setting but I'd be happy to work something out over a private channel. You can find my email on my GitHub profile if that's possible. (My hunch is that Material-UI is our bottleneck, but I'd love to know for sure!)

amcasey commented 2 years ago

@danvk I sent you an email Feb 25 - sorry for not posting about it here. Unfortunately, if you've replied, I can't seem to find it. Any update on your end? No worries if you're busy - there's a lot going on right now.