Tracking: IDE support / LSP implementation

[kevinramharak]

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

• Support for WebStorm? #11
• Neovim support #21
• Support for Visual Studio 2022? #25
• Hey you, make it work in vim  #26
• CLI support please! #35
• Zed Support #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

• Add an LSP to be able communicate with editors #94
• Migrate to monorepo #51

Resources

• https://microsoft.github.io/language-server-protocol/

[kevinramharak]

As mentioned in the discussion about needed features of VS Code #43 (comment), Diagnostic messages will soon have the option to be of type MarkupContent. This would allow us to implement a Language Service Plugin that sits between TypeScript and the editor.
This would make it a lot easier to support other editors, as they will be supported as long as they implement the LSP as the specification of 3.18 defines.

[kevinramharak]

Well unfortunatly as stated in #43 (reply in thread), we have to wait until TS 6 before we can implement this properly as neither the typescript language server nor the vscode typescript language features extension implement the LSP.

[yoavbls]

This thing is still valuable because other extensions could take the text output and replace the code blocks (markdown or not) with their own way of rendering code blocks.
BTW, Zed editor has already implemented it and I haven't taken a look at the implementation yet