microsoft / microsoft/typescript-analyze-trace
request: something like `--watch` mode
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 429
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
It would be helpful if there was something like --watch mode, or documentation for how to do this.
Example workflow:
- We run
analyze-trace ts-trace - Oh look, a hot spot!
Analyzed /Users/dylang/project/packages/example/tsconfig.json (trace.65458-188.json)
Hot Spots
└─ Check file /Users/dylang/project/packages/example/slow-type-in-here.js (1739ms)
└─ Check variable declaration from (line 57, char 7) to (line 62, char 2) (1441ms)
└─ Check expression from (line 57, char 30) to (line 62, char 2) (1441ms)
└─ Check expression from (line 57, char 30) to (line 57, char 52) (1438ms)
└─ Compare types 13361 and 4729 (1249ms)
- We make a change to try to fix it, and hit save....
This is where this feature request starts.
analyze-traceautomatically runs again. Fewer files may need to be recompiled so analyze-trace is only showing results from those re-compiles. Feature Request- The output from
analyze-tracetells us how much faster or slower each change is compared to the previous run. Bonus Feature Request
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the analyze-trace CLI entry point and trace-analysis workflow, then reproduce the example using a generated TypeScript trace. Done means a watch mode reruns analysis after a file save and reports the requested results; compare-against-previous-run output is an explicitly marked bonus request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100