Need help in setting up TypeScript LSP in Windows

[ajitid]

I'm having difficulty in setting up TypeScript LSP with helix. Here are the steps that I did:

• Installed helix using scoop install helix
• Installed tsserver using npm install -g typescript typescript-language-server
• cd-ed into a TypeScript project and opened it using hx
• Opened a TypeScript file and expected errors and autocompletion to kick in but it didn't

All the command have been run in Powershell (non-admin) mode.

I can confirm that both typescript and typescript-language-server are available in my system PATH. Doing hx -v gives this in Users\<username>\AppData\Local\helix\helix.log:

2021-11-03T03:08:25.849 helix_view::editor [ERROR] Failed to initialize the LSP for `source.ts` { IO Error: The system cannot find the file specified. (os error 2) }

In the log, is it expecting typescript-language-server to be available?

OS: Windows 11 (tried in Windows 10 too)
Helix: 0.5.0

[archseer]

Yeah, that failure occurs when the LSP binary can't be found. Looks like there's a note in the Rust docs:

If program is not an absolute path, the PATH will be searched in an OS-defined way.

The search path to be used may be controlled by setting the PATH environment variable on the Command, but this has some implementation limitations on Windows (see issue #37519).

rust-lang/rust#37519

I think we'll want to use the which crate to resolve to a full path.

Could you try if setting the language server path to an absolute path to the binary would work for you?

languages.toml

[[language]]
name = "typescript"
language-server.command = "full path to binary"

[ajitid]

Adding .cmd solves the issue in Windows.

languages.toml:

[[language]]
name = "typescript"
language-server.command = "typescript-language-server.cmd"

---

Went through the issue you mentioned and also through an LSP installer for Neovim. It does not matter if you are running on PowerShell and could find a .ps1 script file, you would still need .cmd file instead because it is considered as an executable.

[sudormrfbin]

@ajitid Thanks for the detailed addition to the troubleshooting wiki :)

[ajitid]

Anytime!

We have two different spaces in which we are maintaining information — Helix docs and Github Wiki. Are we planning to move away from one of them anytime soon?

[sudormrfbin]

The wiki has the advantage of not requiring PRs for contributing content, so it's perfect for a community knowledge base. I think having both is okay as long as we link them properly.