Closed blikblum closed 2 months ago
Oh, I never used the ts server on Windows, it seems that it's distributed with several binaries with the same name but different extension, the server won't run unless you set the full path of the LSP. With the current ecode version you can go to:
Settings
-> Tools
-> Plugin Manager
-> select/click LSP Client
-> Click Preferences
-> edit the file adding your server configuration, it will look like:
{
"config": {
"disable_semantic_highlighting_lang": [],
"hover_delay": "1s",
"semantic_highlighting": true,
"server_close_after_idle_time": "1m",
"silent": false,
"trim_logs": false
},
"keybindings": {
"lsp-format-range": "alt+shift+f",
"lsp-go-to-declaration": "",
"lsp-go-to-definition": "f2",
"lsp-go-to-implementation": "shift+f2",
"lsp-memory-usage": "",
"lsp-plugin-restart": "",
"lsp-refresh-semantic-highlighting": "",
"lsp-rename-symbol-under-cursor": "mod+shift+r",
"lsp-switch-header-source": "",
"lsp-symbol-code-action": "alt+return",
"lsp-symbol-info": "f1",
"lsp-symbol-references": "mod+shift+u",
"lspz-go-to-type-definition": ""
},
"servers": [
{
"command": "C:\\Program Files\\nodejs\\typescript-language-server.cmd",
"command_parameters": "--stdio",
"name": "typescript-language-server"
}
]
}
The relevant part is the configured server with the full path. A patch to fix this issue will be pushed after this message.
This is a patched ecode that should get the typescript-language-server working out of the box ecode-windows-0.6.0-x86_64.zip.
Works like a charm
Many thanks
Using ecode 0.6 on windows 10
Opening a folder with a js project i receive a notification: "LSP Server typescript-language-server failed to initialize, received some error:"
Installed typescript-language-server using
npm install -g typescript-language-server typescript
as described in typescript-language-server projectLanguages health tool recognizes typescript-language-server
Running
typescript-language-server --stdio
on terminal worksApp log:
System info