yoavbls/pretty-ts-errors

Tracking: Performance Issues

Open

#139 opened on Oct 12, 2025

View on GitHub
 (3 comments) (1 reaction) (0 assignees)TypeScript (81 forks)batch import
help wantedperformance

Repository metrics

Stars
 (11,771 stars)
PR merge metrics
 (Avg merge 1d 14h) (4 merged PRs in 30d)

Description

This issue serves as a central hub for tracking all related performance-related issues and reports.

Goals

  • Find & Fix the causes of reported high CPU loads and freezes
  • Add & Improve logging to aid in finding performance-related issues Fixed with #151
  • Add an issue template with instruction to make reporting new issues easier, and allow for easier and more reliable reproduction of issues Fixed with #173
  • Add (regression) tests to avoid causing the same issues with future changes

Reported issues

Related issues

Related PR's

  • #138

Resources

Contributor guide

Research direction
Start by reproducing one of the linked performance issues, then use VSCode profiling tools to identify bottlenecks. Focus on areas highlighted in #138 and #104. Contribute regression tests after understanding the root cause.
Tech stack
typescript
Domain
developer experience
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
GitVSCode extension development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20