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