Skip to content

Completions not working in Neovim. #1241

Open
@Azpect3120

Description

@Azpect3120

Neovim via NixVim on NixOS
nvim version: v0.10.2 Release

Tailwind CSS
tailwindcss 3.4.14

Installed with home manager like so:

programs.nixvim.plugins.lsp.servers.tailwindcss.enable = true;

Package Manager
bun 1.1.34

Operating System
NixOS with Flakes and Home Manager

Tailwind config

// Basic, but should be enough to get functionality from the LSP
/** @type {import('tailwindcss').Config} */
export default {
  content: ["./src/*", "./src/**/*"],
  theme: {
    extend: {},
  },
  plugins: [],
}

Reproduction Steps

Create a new sveltekit application
npx sv create

Image

Open any `.svelte file and begin entering tailwind classes. You should notice that the LSP does not provide competitions.

Image
This image was taken while in insert mode, attempting to achieve a completion.

Running the LspInfo command can usually help debug these issues. However, nothing here appears to be causing any issues.

Image

Finally, after generating a tailwind.config.js file using bunx tailwindcss init and adding paths, the LSP still does not provide completions.

Image

Samae as before, this image was taken in insert mode, when the LSP SHOULD provide a completion. But this time, we have a config file.

Describe your issue

Autocompletion and intelisense do not work with NixOS in the Neovim plugin. I cannot speak or test if it works on a different Neovim client, but in my system it does not. npx cv create does not generate a tailwind.config.* file, but when creating one with bunx tailwindcss init and adding the paths to my sources, it still does not provide completions. The LSP is connected, as seen in the images above, a common pitfall of self-configured LSP clients in Neovim.

I recall this working not too long ago (I cannot remember how long; I haven't used web tech in a while), so I am confident it is not a config-based issue. However, I am open to hearing ideas. Furthermore, every other LSP I use works perfectly with the same simple setup outlined above.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions