yoavbls/pretty-ts-errors

Tracking: IDE support / LSP implementation

Open

#145 opened on Oct 13, 2025

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

Description

This issue serves as a central hub for tracking all requests and discussions about support for editors other than VS Code and the implementation of the Language Service Protocol

Summary

There have been various requests to support other editors and for a cli version. These implementations are now scattered across forks. Some support is implemented with the @pretty-ts-errors/formatter package.

Reported issues

Related projects & forks

Related PR's

Resources

Contributor guide

Tech stack
typescript
Domain
developer experiencetoolingcli
Issue type
feature
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScriptLanguage Server ProtocolNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Examine the existing forks and PRs listed in the issue to understand current implementations. Focus on the @pretty ts errors/formatter package and how it could be extended into an LSP. Look at the LSP specification and existing TypeScript LSP examples to design a modular approach. Start by reviewing PR #94 and #51 for progress.