Intellisene doesn't work in LazyVim

[leoyhk]

What version of VS Code are you using?

LazyVim

What version of Tailwind CSS IntelliSense are you using?

LSP version is 0.0.14 (installed with Mason)

What version of Tailwind CSS are you using?

3.3.5

What package manager are you using?

pnpm

What operating system are you using?

MacOS Sonoma 14.2

Tailwind config

import type { Config } from "tailwindcss";

export default {
  content: [""],
  theme: {
    extend: {},
  },
  plugins: [],
} satisfies Config;

VS Code settings

{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "explicit"
  },
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true,
  "eslint.rules.customizations": [{ "rule": "*", "severity": "warn" }],
  "eslint.workingDirectories": [
    { "pattern": "apps/*/" },
    { "pattern": "packages/*/" }
  ],
  "typescript.tsdk": "node_modules/typescript/lib",
  "typescript.enablePromptUseWorkspaceTsdk": true,
  "tailwindCSS.experimental.configFile": "./packages/config/tailwind/index.ts",
  "[prisma]": {
    "editor.defaultFormatter": "Prisma.prisma"
  }
}

Reproduction URL
https://github.com/leoyhk/tailwind-lsp-not-working/tree/main

Describe your issue
IDE: Lazyvim

LSP Version: 0.0.14 (Installed with Mason)

Bug observed: LSP does not work when "tailwindCSS.experimental.configFile": "./packages/config/tailwind/index.ts", is active in .vscode/setting.json

Expected behavior: LSP provides suggestions and auto completion

How to Recreate:

1. Open the dir with nvim (i'm using the Lazyvim distribution), open any .tsx file. LSP does not provide any TailwindCSS related suggestions when typing the classnames.
2. Enter .vscode/setting.json and comment "tailwindCSS.experimental.configFile": "./packages/config/tailwind/index.ts"
3. Restart nvim and open any .tsx file, the LSP should work normally
   P.S. I'm searching for a solution / config that could make LSP work in lazyvim/nvim without changing the project settings (since it is a team project), i.e. i shall not treat commenting the line as the solution.

LspInfo shows tailwindcss is up and running, but no suggestions are given while typing

[rmerli]

Currently having the same issue, I checked the LspLog and when starting the lsp server I get this error:
[ERROR][2024-02-05 19:02:38] ...lsp/handlers.lua:535 "Unhandled exception: Bad file descriptor\nError: Bad file descriptor"

[rob32]

same here with django (htmldjango)

...lsp/handlers.lua:535 "Unhandled exception: Bad file descriptor\nError: Bad file descriptor"

[Picalines]

I came across the same thing while working on my project. The application is wrapped in Docker, the database container saves files to a local volume. I cloned the repository onto 2 machines and downloaded identical nvim configurations and tailwind LSPs. The tailwind LSP works correctly only where docker has not yet created the volume. On another machine, a line appears in the logs:

[ERROR][2024-05-14 18:21:02] ...lsp/handlers.lua:535	"Unhandled exception: Bad file descriptor\nError: Bad file descriptor"

The local volume folder definitely has special file permissions; repro in #815 shows how, due to some file permissions, the server receives an unhandled exception

Thoughts on this: perhaps the tailwind server should not look in directories ignored by git? I did not open files in volume on purpose - maybe the server is trying to get a list of files available to it?

[zackAJ]

latest updates broke it for me as well, I use Neovim btw.

[ar7casper]

@leoyhk Have you found a solution?

[rmerli]

My issue is related to the permission of a docker generated folder. I have a postgres container and it creates a data folder where postgres is the owner. For some reasons tailwind tries to access it and is it causing the error. My current very annoying solution is to chmod the folder every time I bring up the container. Hopefully it will get fixed soon, idk

[thecrypticace]

The original issue here is very likely a configuration problem with the neovim LSP setup — though I can't speak to exactly what that issue is. I've got a setup with LazyVim on Ubuntu 22 that's working perfectly (based on the repro from #815).

Aside, about the "bad file descriptor", the only way I've seen this happen is if:

• You're on linux;
• Your LSP client does not support watching for changed files;
• Your environment supports Parcel Watcher;
• The workspace folder being passed to the language server does not exist or isn't accessible
• (note: macOS does produce something similar but the error message is actually descriptive)

In which case we'll get through some initialization steps, eventually attempt to initialize Parcel Watcher, and it throws that error. This does prevent the workspace folder from initializing but in a multi-root workspace the others should still initialize if they're valid and accessible. Also, if the client sends a workspace folder change event we'll still attempt to re-initialize the folder so the server itself is still responding to requests as expected.

I can't get this to happen where the server stops working. I could do an fs.access(…) on the workspace folder for a better error message but that's about it (I've done that in #1276).

Notably, I'm also unable to reproduce the case of a folder that contains files and/or folders with other permissions causing completions to stop working — even with the reproduction in #815. I used an Ubuntu VM through Parallels on macOS (Apple Silicon) and WSL2 (Ubuntu 24.04.2 LTS) on Windows 11 on x86_64 (AMD Ryzen 3700X).

Gonna close this one — if someone can provide another reproduction though I will definitely take a look.