microsoft / microsoft/typescript-analyze-trace
Feature: Program Construction
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 429
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
We can already detect and report program building hot-paths (chiefly in findSourceFile), but the output is confusing. We would need to identify imports with high self time and then report causal chains for those.
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 with the existing hot-path reporting around findSourceFile and inspect sample output from tsc --generateTrace. Determine how imports with high self time should be identified and how their causal chains should be represented. Done means program-construction output clearly reports those imports and their causes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100