ts-error-translator-proxy

An LSP proxy that translates TypeScript errors into human-readable explanations. Works with any editor.

Based on Matt Pocock's ts-error-translator. Inspired by ts-error-translator.nvim.

Zed Helix

Why a proxy?

ts-error-translator.nvim works great for Neovim. If you use Helix, Zed, or another editor, you need a different approach.

This proxy wraps any TypeScript LSP and intercepts diagnostics. No editor plugins required.

Installation

cargo install ts-error-translator-proxy

Or from source:

git clone https://github.com/yourusername/ts-error-translator-proxy
cd ts-error-translator-proxy
cargo build --release

Usage

ts-error-translator-proxy [OPTIONS] [LSP_COMMAND] [LSP_ARGS...]

# Wrap vtsls (default)
ts-error-translator-proxy

# Wrap typescript-language-server
ts-error-translator-proxy typescript-language-server --stdio

# Replace mode
ts-error-translator-proxy --replace vtsls --stdio

Editor Configuration

Helix

~/.config/helix/languages.toml:

[language-server.vtsls-translated]
command = "ts-error-translator-proxy"
args = ["vtsls", "--stdio"]

[[language]]
name = "typescript"
language-servers = ["vtsls-translated"]

[[language]]
name = "tsx"
language-servers = ["vtsls-translated"]

Zed

~/.config/zed/settings.json:

{
  "lsp": {
    "vtsls": {
      "binary": {
        "path": "ts-error-translator-proxy",
        "arguments": ["vtsls", "--stdio"]
      }
    }
  }
}

Neovim

Neovim users should use ts-error-translator.nvim instead.

Other Editors

This should work with any editor that supports LSP. PRs with examples welcome.

License

MIT