yoavbls/pretty-ts-errors

symbol links can point to wrong symbol when error message is a duplicate, but differs in type.

Open

#143 opened on Oct 13, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (81 forks)batch import
buggood first issue

Repository metrics

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

Description

Describe the bug After adding examples/example.js I noticed the symbol link is bugged when you happen to have identical error messages, that happen to be unrelated. It is a very niche case that probably does not happen in real world applications, but something to fix nonetheless.

Expected behavior I expect the formatted error message to reference the correct symbol for both errors.

Observed behaviour The formatted error message may reference the incorrect symbol, depending on which error message happens to be formatted and cached first.

Screenshots The reference should point to the Person type in the same file (blue line), instead depending on a duplicate formatted message that may be cached it could point to the wrong file (red line).

Contributor guide

Research direction
Examine the caching logic for formatted error messages to understand how duplicate messages are stored and retrieved. Trace how symbol links are resolved to ensure they point to the correct symbol type, not just the message text.
Tech stack
typescript
Domain
developer experiencetooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70