tracer
tracer copied to clipboard
tsperf
A VSCode extension to measure type complexity within a project.
Automatically switching saves in the persistent storage to the current head label would be an easy way to have traces and trace diagnostics match the current code It is possible...
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...
Settings can be made much easier for the user to manage with a dedicated component in the UI instead of the generic vscode settings panel. It is likely that different...
Doing in process traces using ts lib would allow us to provide more information in an on-demand manner. For example, types.json only includes the display field when it is cheap...
does this work as well for you, when using the 'Debug: Start debugging' command in vscode?
Currently the trace data functionality is not providing a lot of value, but I believe it can with better display and interactivity. potential improvements: * my intervals branch displays the...
More data is needed in trace files to enable better performance analysis. For starters, adding a timestamp to types.json lets us report types created during a timeframe and associate them...
After running "Tracer: tsc trace" I can get warnings on extremely innocuous lines:  Of particular note: ```ts export type ConstructorOf = new ( // eslint-disable-next-line @typescript-eslint/no-explicit-any ...args: any[] )...
Just highlighting depth limits in the trace could be helpful to point out potential performance issues. Automatic suggestions may also be possible. For example, LukeAbby on discord mentioned that adding...
When I try to run the `tsc trace` command, I get the following error: > C:\Users\daelon\AppData\Roaming\Code\User\globalStorage\tsperf.tracer\godot-tools>(cd 'p:\\_godot\godot-vscode-plugin'; npx tsc --noEmit --generateTrace 'c:\Users\daelon\AppData\Roaming\Code\User\globalStorage\tsperf.tracer\godot-tools\default\traces') > The filename, directory name, or volume label...
