yoavbls / yoavbls/pretty-ts-errors
Tracking: IDE support / LSP implementation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14.1k
- Forks
- 111
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 5
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
- https://github.com/yoavbls/pretty-ts-errors/issues/11
- https://github.com/yoavbls/pretty-ts-errors/issues/21
- https://github.com/yoavbls/pretty-ts-errors/issues/25
- https://github.com/yoavbls/pretty-ts-errors/issues/26
- https://github.com/yoavbls/pretty-ts-errors/issues/35
- https://github.com/yoavbls/pretty-ts-errors/issues/95
Related projects & forks
- https://github.com/voxpelli/pretty-ts-errors-cli
- https://github.com/hexh250786313/coc-pretty-ts-errors
- https://github.com/hexh250786313/pretty-ts-errors-markdown
- https://www.npmjs.com/package/pretty-ts-errors-lsp
- https://github.com/OlegGulevskyy/better-ts-errors.nvim
- https://github.com/youyoumu/pretty-ts-errors.nvim
Related PR's
- https://github.com/yoavbls/pretty-ts-errors/pull/94
- https://github.com/yoavbls/pretty-ts-errors/pull/51
Resources
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by reviewing the reported issues, related forks and pull requests, and the Language Server Protocol resource; the body names no source files or tests. Before implementation, narrow the work to one editor or CLI/LSP target and define completion as support for that target, since this tracking issue has no single done condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- cli, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100