Autocomplete not working in apps directory with Tailwind v4 and plugin version 0.14.17 on Next.js Turborepo

[addegbenga]

What version of VS Code are you using?

v1.100.2

What version of Tailwind CSS IntelliSense are you using?

For example: v0.14.17

What version of Tailwind CSS are you using?

v4.0.8

What package manager are you using?

pnpm

What operating system are you using?

macOS

Tailwind config

/** @type {import('postcss-load-config').Config} */
const config = {
  plugins: { "@tailwindcss/postcss": {} },
};

export default config;

VS Code settings

{}

Reproduction URL

A public GitHub repo that includes a minimal reproduction of the bug. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways.

Describe your issue

I am using Tailwind CSS v4 on a Next.js Turborepo project. Autocomplete only works in my packages/ui directory but does not work in my apps directory. After further investigation, I discovered that this bug was introduced in the latest plugin version: 0.14.17. Autocomplete works as expected with version 0.14.16.

Steps to Reproduce

1. Set up a Next.js Turborepo with Tailwind v4.
2. Update the plugin to version 0.14.17.
3. Observe that autocomplete only works in packages/ui but not in apps.
4. Downgrade the plugin to 0.14.16 and see that autocomplete works in both directories.

Expected Behavior

Autocomplete should work in both packages/ui and apps directories regardless of the plugin version.

Actual Behavior

Autocomplete only works in packages/ui when using plugin version 0.14.17. It does not work in apps.

Additional Context

• Tailwind CSS v4
• Next.js Turborepo structure
• Plugin: 0.14.17 (broken), 0.14.16 (works)

Please let me know if more information is needed.

[thecrypticace]

Can you test 0.14.18 and see if your issue is fixed?

[addegbenga]

Can you test 0.14.18 and see if your issue is fixed?
I just tested it now, and it's still not fixed.

[thecrypticace]

@addegbenga

1. Can you provide a reproduction project as I'm not able to reproduce this?
2. Could you provide the logs from running the command "Tailwind CSS: Show Output"?

[B-HS]

Same error occurred and I also fixed by downgrade to 0.14.16 from 0.14.19.
I also almost same environment 1.100.2, next js 15 app router, pnpm, macos, and monorepo by pnpm.

In my case also same, works for ui/ (library) which located in same depth with www/ (nextjs)
but intelisense is not working for www/.

below is output when try to autocomplete

[Trace - 1:57:16 PM] Sending request '@/tailwindCSS/getProject - (39)'.
Params: {
    "uri": "file:///{PATH_FOR_PROJECT}/www/src/app/test/page.tsx"
}
[Trace - 1:57:16 PM] Received response '@/tailwindCSS/getProject - (39)' in 1ms.
No result returned.

[timmywil]

I was seeing the same or similar issue and found #1033 by searching for the error [GLOBAL] No matching project for document. Downgrading to v0.14.16 also works for me. FWIW, intellisense works in standard CSS and HTML files, but not all file types. In my case .ex and .heex were broken, but probably has the same issue as .tsx and .jsx. And again, it is a regression beginning in v0.14.17. I am using Tailwind 4.1.7.

[0-CAT]

Unfortunately, I am using Tailwind with Zed editor which doesn't support downgrading the version of LSPs.

I can share that my logs find zero projects to initialize with on startup:

Setting up server…
Listening for messages…
Language mappings are currently set via initialization options (`userLanguages`). This is deprecated and will be removed in a future release. Please use the `tailwindCSS.includeLanguages` setting instead.
Searching for Tailwind CSS projects in the workspace's folders.
[Global] Creating projects: []
[Global] Preparing projects...
[Global] Initializing projects...
[Global] Initialized 0 projects

Not sure if that deprecation warning is related, but I would assume not (since it's just a warning and not an error).

But then I get this output for every file I open:

[GLOBAL] No matching project for document {
  fsPath: '/path/to/file.tsx',
  normalPath: '/path/to/file.tsx'
}

In the LSP info, I see that the Registered workspace folders path is correct. I'm using tailwindcss@4.1.7 as well, and it looks like the LSP version is v0.14.19.

Autocomplete only works in packages/ui when using plugin version 0.14.17. It does not work in apps.

Mine actually does not work anywhere in the repository, so not sure what the difference is in my case.

[David2k13]

I also met, can only work in 0.12.18

[thecrypticace]

@0-CAT

Not sure if that deprecation warning is related, but I would assume not (since it's just a warning and not an error).

Nah, it's not. I need to make a PR to Zed to change how they pass that stuff through by default but just have not done that yet.

[Global] Creating projects: []

This tells me that it can't find any Tailwind CSS configs in your project. Could you share a reproduction? It would be super helpful to figure out what you're expecting to work and why the server can't find anything.

I am using Tailwind with Zed editor which doesn't support downgrading the version of LSPs.

You can! (sorta). I use Zed every day with a local build of the server. If you install the language server yourself globally (or really just in any folder somewhere) you can specify a custom language server path in your settings:

  "lsp": {
    "tailwindcss-language-server": {
      "binary": {
        "path": "/path/to/your/node/binary",
        "arguments": [
          "/path/to/your/global/node_modules/.bin/tailwindcss-language-server",
          "--stdio"
        ]
      },
      "settings": {
        "tailwindCSS": {
          "classFunctions": ["clsx"] /* this just an example to show settings,  you don't need these if you don't want them */
        }
      }
    },
  }

The relevant NPM package is @tailwindcss/language-server

@David2k13 Can you please provide a reproduction and logs (if in VSCode "Tailwind CSS: Show Output")

[0-CAT]

This tells me that it can't find any Tailwind CSS configs in your project. Could you share a reproduction? It would be super helpful to figure out what you're expecting to work and why the server can't find anything.

I can try to put together a minimal reproduction tomorrow, but for now: my setup was pretty much just using npx create-turbo@latest and then setting up Tailwind with the postcss process.

From what I saw in the LSP ReadMe and the relevant source code, for Tailwind 4 it just needs a .css file that has a Tailwind import in it, which I do have:

It did previously work a few weeks back with Zed, so something definitely changed.

If you install the language server yourself globally (or really just in any folder somewhere) you can specify a custom language server path in your settings

Might give this a try tomorrow, too, and see if v0.14.16 works as expected.

[zigang93]

solve with version 0.14.14

[stempest0925]

Me too, created through "create-next-app", using tailwind 4 and tailwind plugin 0.14.19, auto completion plugin does not work.

[bohdan-basov]

Works in 0.14.16. Still broken in 0.14.19

[thecrypticace]

@bohdan-basov @stempest0925 Can either of you provide a reproduction repo I can clone, system information, VSCode settings, etc…?

I'd really like to help solve whatever these problems are you're having but I can't without having actionable information. I test these processes all the time and don't generally encounter problems.