LSP not working neovim

[codePassion-dot]

What version of VS Code are you using?

not using vscode, using neovim

What version of Tailwind CSS are you using?

v3.3.2

What package manager are you using?

npm

What operating system are you using?

linux

Tailwind config

/** @type {import('tailwindcss').Config} */
module.exports = {
  content: [
    "./pages/**/*.{js,ts,jsx,tsx,mdx}",
    "./components/**/*.{js,ts,jsx,tsx,mdx}",
    "./app/**/*.{js,ts,jsx,tsx,mdx}",
  ],
  theme: {
    colors: {
      purple: "#7C5DFA",
      "purple-light": "#9277FF",
      "blue-pale": "#373B53",
      blue: "#1E2139",
      "blue-medium": "#252945",
      "blue-light": "#7E88C3",
      white: "#F8F8FB",
      "gray-light": "#DFE3FA",
      "gray-medium": "#888EB0",
      dark: "#0C0E16",
      "dark-medium": "#141625",
      orange: "#EC5757",
      "orange-light": "#FF9797",
    },
    extend: {
      backgroundImage: {
        "gradient-radial": "radial-gradient(var(--tw-gradient-stops))",
        "gradient-conic":
          "conic-gradient(from 180deg at 50% 50%, var(--tw-gradient-stops))",
      },
    },
  },
  plugins: [],
};

Reproduction URL
any project just install the lsp and it's broke right now without doing anything

Describe your issue

install tailwindcss lsp, open project with tailwind no lsp and error:
 Error 10:38:02 PM msg_show.lua_error Error executing vim.schedule lua callback: ...b/v0.9.1/nvim-linux64/share/nvim/runtime/lua/vim/lsp.lua:1309: RPC[Error] code_name = InternalError, message = "Request initialize failed with message: Bad file descriptor"
stack traceback:
[C]: in function 'assert'
...b/v0.9.1/nvim-linux64/share/nvim/runtime/lua/vim/lsp.lua:1309: in function ''
vim/_editor.lua: in function <vim/_editor.lua:0>

[nick-vicinity]

Hello, I am having the same issue. tailwindcss lsp installed via Mason in Neovim.

[jacobo-jaramillo]

Yesterday trying to figure out what was happening I discover that is not happening in all my projects, trying to use it in old projects it works great and creating another nextjs app from scratch works too but in some projects don't and it's weird because all of the projects are just nextjs no more than that so I haven't figured out why it's working in some of them, maybe cache ?

[dino-rodriguez]

Getting this issue as well - just installed via Packer and configured default.

[johnrazeur]

Got the same issue, it's not working in a monorepo in a nextjs package, but it's working on another package not using nextjs on the same monorepo.

[9mm]

I'm getting this error in Neovim in a vue file

[LeNei]

I had a similar issue that was resolved by updating the tailwindcss lsp. It seems like create-next-app now configures tailwind with a tailwind.config.ts file instead of a tailwind.config.js file which resulted in my lsp not finding the root correctly. Maybe that helps someone :)

[sethtrain]

I've not figured out what the cause was but I did install the latest nightly build (of neovim) and it seems to have fixed the issue.

[koosty]

Same here. Using Lazyvim + Mason

    ◍ tailwindcss-language-server
      ▼ Displaying full log
        The system cannot find the path specified.
        Wrote to C:\Users\john\AppData\Local\nvim-data\mason\staging\tailwindcss-language-server\package.json:
        
        {
          "name": "@mason/tailwindcss-language-server",
          "version": "1.0.0",
          "description": "",
          "main": "index.js",
          "scripts": {
            "test": "echo \"Error: no test specified\" && exit 1"
          },
          "keywords": [],
          "author": "",
          "license": "ISC"
        }
        
        
        spawn: npm.cmd failed with exit code 1 and signal 0. 
 

[hansemschnokeloch]

Same here, but I may have found why. I only have the issue if the project directory contains files that I don't own.
Changing the owner of the files solves the issue in my case.

[big-hero-dev]

Same here, but I may have found why. I only have the issue if the project directory contains files that I don't own. Changing the owner of the files solves the issue in my case.

This working, my Docker created directory, tks.

[dioklecijan]

What NodeJS version are you using? I switched from v14 to v18 and the problem is gone.

[badmagick329]

Same here, but I may have found why. I only have the issue if the project directory contains files that I don't own. Changing the owner of the files solves the issue in my case.

Thank you. After an hour of trying to figure out what was causing the issue, this is what helped. Running a postgres db with docker that had a different owner

[mttrms]

Same here, but I may have found why. I only have the issue if the project directory contains files that I don't own. Changing the owner of the files solves the issue in my case.

This working, my Docker created directory, tks.

I experienced the same. Using Remix Blues Stack and docker creates a postgres-data directory.

I ended up having to adjust docker permissions and permissions/owner for that folder to get the errors to go away and get tailwind lsp working.

What version of VS Code are you using?
N/A - NVIM v0.9.1

What version of Tailwind CSS are you using?
v3.3.3

What package manager are you using?
npm

What operating system are you using?
Ubuntu 22.04.3 LTS x86_64
Kernel: 5.15.0-87-generic

Tailwind config

import type { Config } from "tailwindcss";

export default {
  content: ["./app/**/*.{js,jsx,ts,tsx}"],
  theme: {
    extend: {
      colors: {
        'alphabet-blue': '#011627'
      }
    },
  },
  plugins: [],
} satisfies Config;

[thecrypticace]

Hey, so @RobinMalfait who works here also uses Neovim everyday and doesn't encounter any issues. Additionally, several of the issues listed here have been fixed by either updating Neovim or look to be related to file ownership and permissions which is, of course, not something we can do anything about.

I'm going to close this for now but if you encounter further problems using our Language Server with Neovim and can provide:

1. A repository that you can clone and reproduce these issues in
2. Details in your Neovim setup / configuration
3. OS info

I'll happily take another look!