a tool for diagnosing and fixing TypeScript performance problems
the nice thing is, you can't hide from TypeSlayer (even if you //@ts-ignore or //@ts-expect-error)

run:

npx typeslayer

in the root package you want to inspect (i.e. colocated to your package.json). The tool will:

1. start a local web UI,
2. run TypeScript tooling to produce traces and CPU profiles
3. provide interactive visualizations (treemaps, force graphs, speedscope/perfetto views) that you can use to identify problems

• "but I just want to see my code"
• why do I see lots of <anonymous> everywhere?
• what about tsgo?
• what about Svelte or Vue?
• where does TypeSlayer store my data?
• how sensitive is the data in the outputs?
• does TypeSlayer track me?
• why does the Type Graph keep moving?
• how is testing a library different?
• this is a lot. where do I start?
  • 1. is there actually a problem?
  • 2. is there an outlier in the Treemap?
  • 3. does anything look weird in Perfetto?
  • 4. are there any Award Winners that stand out?
  • 5. sometimes, you still gotta RTFM
• can I pay you to help me? 💸
• but I refuse to run postinstall scripts..
• why isn't this a CLI tool?
• how do I use this with a monorepo?
• what if I already have trace files?
• who needs this stupid thing, anyway?
• what if it's been going for a long time?

TypeSlayer supports Linux x64 (glibc 2.39+), macOS ARM64 (Apple Silicon), and Windows x64. Please note that next year is the year of the Linux desktop 📯.

1. all commits (and therefor PR merges) must be the next bar from (削除) "My Name Is" (complete) (削除ここまで) "The Real Slim Shady" by Eminem, until further notice
2. no further requirements

this app is built with Tauri, TanStack, Vite, oxc, React, MUI, Rust, and of course, TypeScript.