Autocomplete doesn't work

[chrisolsen]

• I am using ctrl+space. A "Loading..." temporarily pops up, but nothing happens after that
• I do have all the LSPs installed
• LspInfo looks ok
• npm libs are installed (image 4)
• LSPs initialize when opening file (image 5)

Any ideas to what is not right?

[SetsuikiHyoryu]

I compared the diagnostic information and noticed that the Settings for your ts_ls is set to vim.empty_dict(). Could you try removing that?

If it still fails, please share the configuration for ts_ls.

[chrisolsen]

Thanks for the response.

Here is my init.lua file https://gist.github.com/chrisolsen/6f0f83fdd610ca7a2ad2e804868a4b09

Currently there are no props defined in the ts_ls

local servers = {
  gopls = {}, ts_ls = {}, svelte = {}, cssls = {}, html = {}, htmx = {}, prettier = {}, eslint = {}, emmet_ls = {},

  lua_ls = {
                settings = {
                    Lua = {
                        completion = {
                            callSnippet = "Replace",
                        },
                    },
                },
            },
 }

• I just noticed that ts_ls appears twice in that list with a matching buffer of 38. Would that cause any issues?
• I also noticed that the issue only seems to be for the npm installed libs (ts, svelte, html, css, etc) as gopls and lua work properly.

[SetsuikiHyoryu]

Your configuration looks a bit outdated.

If gopls and lua are working fine, it might be because your Neovim version is < 0.11.
Having ts_ls appear twice is also abnormal, but I’m not too sure how it’s supposed to be configured in older versions.

If you’re not particular about sticking with your current Neovim version, my suggestion is to update Neovim to >= 0.11
and then configure LSP according to #1475.

[chrisolsen]

I am using Neovim 0.11.4. As for the the kickstart init.lua file, It was created just a couple weeks ago, which was after the most recent commit. The snippet above contains the lsps that I added along with some edits to clean things up pre-paste.

[chrisolsen]

Just for clarity, when setting up an LSP am I responsible for installing the library via npm i -g ... (which I currently have done) or does Mason install it when I select the LSP from the list?

[SetsuikiHyoryu]

When you select an LSP in Mason’s interface, Mason will install it.

The current issue is that Neovim changed its LSP API starting from version 0.11,
so Mason correspondingly updated to V2, which also changed the way it uses the LSP API.

However, kickstart.nvim has not yet merged any changes to adapt to this,
so you’ll need to refer to the PR and configure it manually.

[chrisolsen]

I will give that a go. Thanks for the help