yoavbls/pretty-ts-errors

Tracking: Performance Issues

Open

#139 opened on Oct 12, 2025

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

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

Tech stack
typescript
Domain
performance
Issue type
performance
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.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
TypeScript knowledgeVSCode extension basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
This is a meta tracking issue for performance problems. Start by examining the linked issues (#75, #88, #102, #118) detailing high CPU loads and freezes. Review the related PR #138 which adds logging for performance diagnosis. Consult the provided VSCode performance wiki. The goal is to identify common patterns, propose specific fixes, or write regression tests. Focus on reproducing issues and locating performance critical code paths in the extension.