4 Replies
The Deno LSP ships with its own instance of tsserver and is thus not compatible with tsserver alone. I'm not sure how it works in neovim, but at least in vscode the deno extension disables vscode's built in tsserver if a Deno project is detected
Hm
Did you already see the suggestion about setting a root_dir value for each server, ts and deno's.
https://docs.deno.com/runtime/manual/getting_started/setup_your_environment#neovim-06-using-the-built-in-language-server
Yeah, i got it working