microsoft / microsoft/typescript-analyze-trace
I rewrote this tool in Rust (but also TypeScript)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 429
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
hey just wanted to mention that I rewrote this tool in much more modern TypeScript and fixed a few things along the way and publish it here https://www.npmjs.com/package/@typeslayer/analyze-trace
that said, one thing I didn't keep in my version was the node streaming stuff (which is necessary to process files over 600mb or so, which is around the maximum size of a string in JavaScript). what I did do, though, instead, is... rewrite it in Rust. that solved all my problems and also it's like way way way faster too. see here https://github.com/dimitropoulos/typeslayer/tree/main/packages/typeslayer/src-tauri/src/analyze_trace
happy to hear feedback. this is a cool tool and I needed to expand upon it for TypeSlayer.
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
No in-repository file or test is named. Start by reviewing the linked TypeScript package and packages/typeslayer/src-tauri/src/analyze_trace; clarify whether any change is wanted, then define a repository entry point and validation before work can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100