Some languages have incorrect startup paths

[dxy2233]

I've searched open issues for similar requests

• Yes

I've manually reviewed logs to find potential errors

• Yes

I've recently downloaded the latest plugin version of mason.nvim

• Yes

Problem description

As shown in the image.
The annotation content is the generated invocation path when downloading that language.
The non-commented part is the modified path that can be correctly invoked.

The operating environment is within WSL 2 with Arch Linux, and I'm unsure if it's influenced by other configurations.

Expected behavior

Configure the correct path.

Steps to reproduce

After the default installation, it is not possible to use it. Opening the log information indicates that the path content is not found.

Affected packages

all

Neovim version (>= 0.7)

0.9

Operating system/version

wsl2, arch

Healthcheck

No problem

Screenshots or recordings

No response

[williamboman]

I'm having some difficulties understanding what the issue is.

Is it correct that in the image you've provided, the visible buffer displays the contents of ~/.local/share/nvim/mason/bin/vue-language-server?

Can you also provide :checkhealth contents? What version of npm do you have installed?

[dxy2233]

Some languages have incorrect invocation paths after installation, such as vue-language-server and emmet-ls.

checkhealth may be no problem.

[williamboman]

I don't recognize the script contents of the executable (this is provided entirely by npm). Due to how it's implemented (it relies on relative paths from the executable itself) it's not compatible with the symlinking of executables that Mason does. I will need to investigate exactly what happens on WSL.

[Trildar]

The script is a shim script that npm normally outputs on Windows. The logic to output shims vs creating symlinks can be seen here: https://github.com/npm/cli/blob/latest/node_modules/bin-links/lib/link-bins.js

I think what happened is that the Windows-installed npm was called when Mason installed the packages for these language servers, which causes the shims to be output instead of symlinks. I encountered this myself, and after installing Node in WSL, thus making npm invoke an instance installed in WSL, the npm packages installed by Mason then had symlinks in .bin and everything works correctly.

[powN1]

Ran into the same issue on WSL2 (Ubuntu 22.04). The path was wrong and had to manually change it (tsserver and pyright) just like OP did. I also run the same configuration on windows 10 and it works without any problems.

[Trildar]

@powN1 Did you have npm installed on Windows? Did you also have it installed in WSL? If you had it installed in both, does which npm give you the one installed in WSL?

[tchaudhry91]

I can confirm that this was the cause for me as well.
WSL was preferring the npm installed via scoop in windows over the one I had locally installed in WSL. Once I fixed that and which npm started reporting the local one. Everything works as expected.
Thanks @Trildar for the tip.