LSP server not starting automatically

[major-winter]

Hi, I'm using Neovim with vim-lsp and vim-lsp settings. I'm able to download the lsp, typescript-language-server in this case, but it does not start automatically when I switch between two different filetype. Is there a way to start the lsp manually or any config that would help me to achieve that?

[mattn]

Could you please provide step to reproduce your issue?

[major-winter]

Hi, I just install the lsp using :LspInstallServer command. The server is installed successfully but doesn't start automatically when I enter the file. You can see the picture for reference.

[mattn]

What is your filetype?

[major-winter]

it's javascript, and I've already added let g:lsp_settings_filetype_javascript=['typescript-language-server'] option in my .vimrc.

[mattn]

when I switch between two different filetype

What do you mean ?

[major-winter]

I mean that if the typescript-language-server is running when I'm in a js file and I switch to another filetype different than js. When I move back to the js file I was working on, the server is not running anymore.

[mattn]

AFAIK, vim-lsp and vim-lsp-settings (at least vim-lsp-settings) does not considers changing filetype.

[mattn]

But I'm thinking it's better to be supported.

[Daghall]

I am using vim 8.2, and I have a similar issue, where files in some folders (git repositories) just would not trigger a server start.

I did some crude debugging and found that for the folders where it did not work, the server_info["blocklist"] contained ["typescript","javascript","typescriptreact","javascriptreact"], whereas the folders where it works, this list is empty.

All files had server_info["allowlist"] equal to ["javascript","javascriptreact","typescript","typescriptreact","typescript.tsx"]] when opening.

I traced the problem to vim-lsp-settings for JavaScript/TypeScript. It looks like the blocklist is populated if there is no node_moduels in any parent directory of the active file, so a quick and dirty workaround for me was mkdir ~/node_modules. 😅 🙈 🤷