feat: handle trace data in extension (#19)

Author: typeholes

.editorconfig

@@ -0,0 +1,15 @@
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+charset = utf-8
+
+[*.js]
+indent_style = space
+indent_size = 2
+
+[{package.json,*.yml,*.cjson}]
+indent_style = space
+indent_size = 2

.gitignore

@@ -24,3 +24,4 @@ logs
 !.env.example
 
 examples/*
+playground/.vscode

.vscode/launch.json

@@ -8,6 +8,7 @@
       "runtimeExecutable": "${execPath}",
       "args": [
         "--extensionDevelopmentPath=${workspaceFolder}",
+        "--profile=TracerDebug",
         "${workspaceFolder}/playground"
       ],
       "outFiles": [

README.md

@@ -6,17 +6,22 @@
 
 🚧 It is a work in progress - help is wanted! 🚧
 
-## How it works
+## Real-time type checking estimates
 
-To avoid the overhead of launching a separate tsserver, it currently queries the VSCode language server to get information about every token in an open file, and uses the timings of the responses as a proxy for the complexity of the types, following the pattern of [`@definitelytyped/perf`](https://github.com/microsoft/DefinitelyTyped-tools/blob/41ba894ba571e55fa91ef0bb0d44d6eb6d201943/packages/perf).
+To avoid the overhead of launching a separate tsserver, it currently queries the VSCode language server to get information about tokens in an open file, and uses the timings of the responses as a proxy for the complexity of the types, following the pattern of [`@definitelytyped/perf`](https://github.com/microsoft/DefinitelyTyped-tools/blob/41ba894ba571e55fa91ef0bb0d44d6eb6d201943/packages/perf).
+
+## Trace file view and metrics
+
+The `Tracer: tsc trace` command can be run to gather accurate timings.  As with real-time metrics, these create diagnostics in the editor open files. It also opens an interface to browse trace files. Editor and UI commands enable navigating between locations in the editor and the trace.
+
+If the trace is run with a version of `tsc` that includes timestamps in `types.json`, type count metrics are also displayed. A PR to include these timestamps or tooling to automatically patch them in are works in progress.  See https://github.com/typeholes/TypeScript/tree/trace-data-5-4 for a version you can build yourself.
 
 ## Help wanted
 
-- Improve UX/API of the plugin - for example, add settings to disable/customise how data is displayed to the user
-- Investigate the possibility of running a TypeScript trace and consuming this data (which would be much more reliable but might take longer)
+- Improve UX/API of the plugin - for example, more settings to customise how data is displayed to the user and better display of the traces
 - Investigate persistent worker threads that watch changes in a project and update asynchronously (and do not need to reinitialise TypeScript)
 - See if it is possible to get extended diagnostics or other diagnostic data from the compiler or tsserver APIs
 
 ## License
 
-[MIT](./LICENSE) License © 2024 [Aleksandra Sikora](https://github.com/beerose) and [Daniel Roe](https://github.com/danielroe)
+Published under the [MIT License](./LICENCE).