v0.12.7 broken

[spacecat]

Installed it just now and I'm not getting any intellisense suggestions and the console complains about the following:

[GLOBAL] No matching project for document

I closed all VS Code windows and terminated the VS Code by "Quitting" my app in my Mac app bar at the bottom.

I reverted back to v0.12.6 and now the extension works again.

Edit: For those that don't know; right click the extension in VS Code Extensions Marketplace and select "Install Specific Version..." and select v0.12.6 to get it working again.

[jaaymes]

me too, downgrade v0.12.6

[OliverGrimsley]

same here, not working inside vue templates, tried a few other suggestions in other issues, not fixed, downgrade to 12.6 restores functionality

[gurenGithub]

me too, downgrade v0.12.6

[josh-dastmalchi]

fwiw deleting the comments in my angular project's styles.scss file and restarting the extension fixed it. but I just rolled back the extension instead.

[lbtoha]

I also facing this issue. Downgrade v0.12.6 is working fine.

[Koyamie]

Same here, if it helps v0.12.7 started erroring when scanning my SCSS files with the following error:

[Error - 2:12:25 PM] Failed to initialize workspace folder .../website e [CssSyntaxError] : .../website/src/styles/bulma.scss:66:1: Unknown word
You tried to parse SCSS with the standard CSS parser; try again with the postcss-scss parser

[EPaulGR]

i had the same problem [Info - 12:38:48] [GLOBAL] No matching project for document { fsPath: '/Users/erickpaulgarciaramirez/Proyectos/front-el-cipres/server.ts', normalPath: '/Users/erickpaulgarciaramirez/Proyectos/front-el-cipres/server.ts' }

[lougreenwood]

👍 - but I get it in the Zed editor from the plain tailwind-language-server

[craxrev]

Like the comment above suggested, deleting inline comments (//) in scss files fixes the issue, you can check logs to see which files have errors

[OliverGrimsley]

@craxrev - problem (at least for me) is that many scss files that have comments are in my vendor folder, so not mine, and will get re-written on an update and fail. Whatever parser they are using is apparently not detecting // or /* comments.

[rodrigo-mahamud]

OMG, all morning wasted trying to figure this one out 🤬.

[Yunlongzzj]

me too, downgrade v0.12.6

[EnettyTech]

Me too, downgrade v0.12.6

[DadvDadv]

same => downgrade v0.12.6

[Rennola]

Wasted a couple of hours on this, downgrade the version

[gugatxr]

Same problem here. downgrade works

[philipp-spiess]

Hey all! Thanks for reporting this and sorry for the troubles! We just released v0.12.8 of the VS Code extension with a fix that resolves this issue. If you still have issues, please let us know!

[EmmanuelOga]

I got the exact same error when using this version: v0.13.38 (pre-release)

I suspect the way to replicate this issue is to put TW config, input.css and some TSX file in mismatching locations. My repo uses a packages folder on the root of the repository.

• packages/frontend/components/my-component.tsx
• packages/server/src/input.css
• packages/server/tailwind.config.js (with content: ["../.../**/*.{ts,tsx}"], or something like that)

... Now open my-component.tsx on VS Code with the TW extension installed, the "No matching project" error appears.

I "fixed it" by moving both tailwind.config.js and input.css to the root folder of the repository.

[vdiaz1130]

This is happening again in a Nrwl Nx Angular monorepo project. Seems the problem started with Tailwind 4 and Intellisense plugin version 0.14.2. Version 0.14.1 works as expected while newer versions beyond that fail with the following message:

Searching for Tailwind CSS projects in the workspace's folders.
{"tailwind":{"version":"4.0.8","features":["css-at-theme","layer:base","content-list"],"isDefaultVersion":false},"path":"/Users/userName/Documents/projects/my-project/tailwind.config.js"}
{"tailwind":{"version":"4.0.8","features":["css-at-theme","layer:base","content-list"],"isDefaultVersion":false},"path":"/Users/userName/Documents/projects/my-project/apps/admin/src/styles.scss"}
[Warn  - 2:12:23 PM] The config /Users/userName/Documents/projects/my-project/apps/admin/src/styles.scss requires a preprocessor and is not supported by Tailwind CSS v4.0.
[Global] Creating projects: []
[Global] Preparing projects...

Note the preprocessor warning "...requires a preprocessor and is not supported by Tailwind CSS v4.0"
[Global] Initializing projects...
[Info  - 2:12:23 PM] [GLOBAL] No matching project for document {
  fsPath: '/Users/userName/Documents/projects/my-project/apps/admin/src/app/app.component.html',
  normalPath: '/Users/userName/Documents/projects/my-project/apps/admin/src/app/app.component.html'
}
[Global] Initialized 0 projects
[Info  - 2:12:23 PM] [GLOBAL] No matching project for document {
  fsPath: '/Users/userName/Documents/projects/my-project/apps/admin/src/app/app.component.html',
  normalPath: '/Users/userName/Documents/projects/my-project/apps/admin/src/app/app.component.html'
}

[tientq64]

The problem still occurs in tailwindcss v4

[leephan2k1]

Version v0.12.6 works for me, thanks to those who suggested it earlier. I don't understand what the heck Tailwind is doing with the new versions anymore.

[Goldbeener]

same => downgrade v0.14.11

[sxlwar]

For me, create a new css file under the project root floder, e.g src/style.css, copy this @import "tailwindcss" into the file, the plugin works.

[YYsuni]

I found that changing the SCSS file to a CSS file resolved the issue.

[MarufZak]

for me that was because i used postcss.config.mjs instead of postcss.config.js with cjs export

[timmywil]

Most recent version that works for me is 0.14.16