Deno Language Server client: couldn't create connection to server. #1188
|
Describe the bug
Versions vscode: |
Replies: 12 comments 1 reply
|
If you do |
|
It is in "$HOME/.deno/bin/deno" and I configured this path to ".vscode/settings.json". Is there a way to use Deno without config the 'deno.path' property inside '.vscode/settings.json'? |
|
It should already work this way - are you sure the VSCode is resolving |
Yes should Work but not!
How can i testing this? |
|
I had deno installed via homebrew and was getting this error. Maybe it will help someone Googling this error. |
Helped me! If it's not an easy fix might be worth sticking a note in the extension description that it doesn't work with homebrew installs. |
Perfect !!!! Thanks |
|
Re-installing deno on ubuntu using similar instructions as mentioned already also solved this for me. |
|
Can we just get the extension accept brew install that doesn't make sense |
|
In my case, I hadn't installed deno with homebrew, but running |
|
This error also happens when Deno is installed via deno-cli through NPM on Windows (this is not an official way of installing Deno, but still, it seems like it doesn't like other types of installations, even if the Deno binary is in Path or added to the Deno: Path vscode config variable). Installing Deno using NPM deno-cli is sometimes useful if you are behind policies that require you to install packages only through a registry proxy, as the proxy validates the deno-cli installation package and allows you to use it. EDIT: I was able to make it work by using the path "C:\Users\USERNAME\AppData\Roaming\npm\node_modules\deno-bin\bin\deno.exe" instead of "C:\Users\USERNAME\AppData\Roaming\npm\deno". |
|
When this occurs it's definitely a user env issue. Let's convert this to a discussion for help. |
It should already work this way - are you sure the VSCode is resolving
${userHome}to the right directory?