We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
feat: add details re diagnostics
chore: format one sentence per line
Callout performance characteristics of ts-server While reading the guide with an eye for improving the editor experience, I was not sure how ts-server behaves, or how fixing hotspots I view during tracing would change the editing experience. I ended up jumping into Discord for clarity, and this is a summary of what I learned.
Remove mention of --trace-ic in favor of dexnode
Updated Performance (markdown)
Fix Performance dropdown closing </details> tag
More "easy-to-compile code" content.
Recommend @typescript/analyze-trace
Fix typo Co-authored-by: Andrew Branch <andrewbranch@users.noreply.github.com>
Clarify why we ask for a tsc trace
Use four-space tabs Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>
Don't refer to "typings" Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>
Remove extra space Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>
Update the Project References section based on recent perf investigations
Tracing tweaks Mainly use a single `about://tracing` URL which works in both Edge and Chrome. Few other minor tweaks (including reducing the very long link texts).
Add TOC link to Performance Tracing
Apply suggestions from code review
Added section about 'Performance Tracing' in the 'Performance' page.