Closed typeholes closed 5 months ago
You can run the trace by clicking on the status bar item or running the "Tracer: tsc trace" command
fixed rare off by one in the goto position in trace and now streaming the tree start nodes in case there are enough to cause lag when sending all at once.
@ssalbdivad pointed out that overlapping error spans were confusing which highlighted that full spans didn't give the user any indication of what positions were in the trace, so I changed to single character spans for the trace diagnostics
Ah you did run the command. If it fails, the error output is shown in the terminal. I set the default trace command to use npx, but that obviously doesn't work for all project. here it should be pnpm. Maybe I should just default to nothing and prompt the user on first trace run?
fixes #22
Moves the data and processing for traces to the extension for better performance.
Also includes the ability to create a mock of the extension panel for ease of development of the UI