LSP refuses to start
See original GitHub issuetest
When starting VS code with a .ts file open, the language server fails to start.
To Reproduce
- Open VS Code
- Open .ts file
- The following toasts pop up:
a.Couldn't start client Deno Language Server
b.A request has failed. See the output for more information.
- The output is as follows:
[Error - 10:12:09 PM] Starting client failed
Launching server using command deno failed.
Expected behavior
The LSP should just run.
Versions
vscode: 1.55.2
deno: 1.9.0 (release, x86_64-unknown-linux-gnu)
extension: v3.3.0 & Canary v0.0.10
deno lsp
runs in the vscode built-in terminal so I know that’s installed correctly.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:13
- Comments:33 (8 by maintainers)
Top Results From Across the Web
Troubleshooting - LSP Mode - LSP support for Emacs
If lsp-mode is unable to find the binary but it is on the path it is probably caused by the fact that emacs...
Read more >Troubleshooting - LSP for Sublime Text
If the server is crashing on startup, try running LSP: Troubleshoot server from the Command Palette and check the "Server output" for potential...
Read more >emacs-lsp/lsp-mode - Gitter
LSP tells me I should lsp-install-server to do this, but I don't see a jdtls option. Ivan Yonchovski ... @yyoncho debug is unable...
Read more >How do I restart a failed language server with built-in LSP?
I am using nvim-lspconfig + built-in LSP functions, and I want to recover from an on_exit failure from my LSP client and restart...
Read more >Rust project, LSP server process fails to start with older GLIBC ...
Rust project, LSP server process fails to start with older GLIBC (< 2.25) · 1. Use e.g. Ubuntu 16.04 LTS ( ldd --version...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This isn’t a fix, but does setting
"deno.path": "/home/digitalkitsune/.deno/bin/deno"
in your VScode resolve the issue?We have some other reports of this (on linux) and haven’t been able to narrow down exactly why it doesn’t work, though
deno
is clearly available in the path. We are likely going to need to add more information to the error handling when we can’t start.