VSCode throws error ⇒ `Hypr client: couldn't create connection to server` even though hyprls is in `$PATH` - Built from source.

[baudneo]

I have built hyprLS from source using Just. I am using visual-studio-code-bin-1.89.1-2 and hyprls is in my PATH.

The full error from vscode when I open hyprland.conf is:
Hypr client: couldn't create connection to server. Launching server using command hyprls failed. Error: spawn hyprls ENOEN

If I open the terminal tab and type hyprls, the hyprls server starts. I am unsure of how I can debug this issue as I don't use vscode often, I use jetbrains products but jetbrains has no support for hyprlang.

So, basically, hyprls is installed and in my $PATH, I can start hyprls by typing hyprls into the vscode terminal or my regular terminal.

What am I doing wrong?

Edit:

❯ hyprls
2024-05-13T22:27:48.655-0600	DEBUG	hyprls/main.go:25	going to start server
2024-05-13T22:27:48.655-0600	DEBUG	hyprls/main.go:18	starting server

[ShyamGadde]

I've encountered a similar issue. However, when I navigated to the .config/hypr directory and initiated VSCode with the command code ., it functioned correctly. The exact cause is unclear, but it seems that Node.js is unable to spawn a new process because it cannot locate hyprls when I open the .config/hypr directory from inside VSCode.

[baudneo]

I've encountered a similar issue. However, when I navigated to the .config/hypr directory and initiated VSCode with the command code ., it functioned correctly. The exact cause is unclear, but it seems that Node.js is unable to spawn a new process because it cannot locate hyprls when I open the .config/hypr directory from inside VSCode.

This worked for me as well. Very strange behaviour, I wonder how this can be worked around for wofi drun? I can't seem to find the .desktop file for vscode.

[ShyamGadde]

I don't think you need to do anything with the .desktop file. I use zsh and I installed hyprls using Go, so I just moved the following from .zshrc to ~/.zshenv and everything works fine now, irrespective of how VSCode was launched.

#GO
export PATH=$PATH:$(go env GOPATH)/bin

[baudneo]

@ShyamGadde Thank you very much for your help, it is greatly appreciated!

[baudneo]

Unfortunately, I compiled hyprls from source so using your workaround does not work for me. I have to use the first workaround (cd to ~/.config/hypr and run code .).

I will update in future once I figure out a solution.

[ShyamGadde]

If you compiled it from source, the most obvious thing I can think of is that ~/.local/bin is not in your $PATH.

So, add something like this in your ~/.zshenv:

# Set $PATH if ~/.local/bin exist
if [ -d "$HOME/.local/bin" ]; then
	export PATH=$HOME/.local/bin:$PATH
fi

Btw, I'm just assuming you use ZSH, if you are using Bash, it's probably going to be a bit different.

[baudneo]

hyperls is already in $PATH using .zshenv, still get the same behaviour.

export PATH=~/.local/bin:"$PATH"

Wonder if there is some vscode setting to solve this?

[baudneo]

Adding to the VSCode integrated terminal env doesn't seem to do the trick either:

This is the fix, adding to the VSCode terminal env. If you are on windows or osx change the .linux to .windows or .osx. Open the command prompt (Ctrl + Shift + P) and type in Preferences: Open User Settings (JSON) and add this:

    "terminal.integrated.env.linux": {
        "PATH": "/home/<USERNAME>/.local/bin:/home/<USERNAME>/.config/hypr"
      }

You may not need to add the .config/hypr directory.

output of vscode terminal $PATH:

❯ echo $PATH
/home/baudneo/git/argc-completions/bin:/home/baudneo/.local/bin:/home/baudneo/.local/bin:/home/baudneo/.config/hypr
❯ hyprls
2024-05-19T14:19:24.771-0600    DEBUG   hyprls/main.go:25       going to start server
2024-05-19T14:19:24.771-0600    DEBUG   hyprls/main.go:18       starting server

So, the setting is applied. I can call hyprls inside of the vscode terminal and it starts the language server. I am thinking the extension must run sandboxed or something and doesnt have access to $PATH.

I had to reboot for things to start working, YMMV.

[baudneo]

OK, this is weird, after a reboot it is now working. I am unsure of what fixed it exactly, I am assuming it was the VSCode terminal path from above.