"tsc" missing from $PATH for typescript-language-server about mason.nvim HOT 5 CLOSED

Hello! This doesn't seem to be an installation issue? I'm not sure I'm following what the problem is, or how typescript-language-server relates to null-ls 🤔

from mason.nvim.

Sorry, I forgot to explain the whole scenario. The built-in tsc diagnostics are configured: https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main/lua/null-ls/builtins/diagnostics/tsc.lua

Which depend on the TypeScript compiler (tsc), which is installed by mason. Funny, because I didn't experience similar issues with the old version of the plugin, maybe something changed?

from mason.nvim.

Ah. No tsc is not installed by Mason (in some cases it is bundled with another package, but it's never exposed "globally").

Which depend on the TypeScript compiler (tsc), which is installed by mason. Funny, because I didn't experience similar issues with the old version of the plugin, maybe something changed?

If I had to guess you probably had tsc installed globally before, and since then you've upgraded/changed your Node version and in doing so lost your old global npm installations?

from mason.nvim.

I guess it's possible, maybe something in the LSP setup changed as well. Not sure. :|

Now I am thinking of it, maybe it would be a good idea to be able to pass a path to the tsc compiler to null-ls itself. This would make sense for other tools managed by mason (for me, now it was either brew or npm -g).

What do you think about that, does it make sense?

from mason.nvim.

I'm pretty sure you can pass an absolute path to null-ls, if you provide the canonical name tsc it will simply look for it in PATH.

from mason.nvim.