-
Notifications
You must be signed in to change notification settings - Fork 214
IntelliSense not working after 0.14.14 update — still broken in 0.14.15 #1309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you provide the output from the "Tailwind CSS: Show Output" command please? |
I have the same issue - using TailwindCSS v3.4.17 with v0.14.15 of the Tailwind CSS IntelliSense extension. It all works fine if I switch back to v0.14.13 Running the "Tailwind CSS: Show Output" command gives me this:
Here's my VSC info:
|
This tells me it takes quite a long time to do a search for CSS files in your project. I suspect this is very large project? Can you provide some more information about your environment, VSCode version, settings, size of your project, OS, etc…? |
I wouldn't call it very large but I guess it depends on your definition of 'very large project'!
I already added some of that info above... could you give me a bit more of a steer on how I'd define 'size of project'? |
Ah whoops I glanced over it my bad. Number of files in the project and size possibly? (A get info in the Finder on the folder you open in VSCode should give both of these pieces of info) Are you working on a shared network drive, your local SSD, or an external spinning disk hard drive? |
It's 218MB (not counting It contains about 15 separate projects - but only two of them use Tailwind - so there are only two tailwind config files in the repo. Both are a couple of folders deep i.e. Each of these two projects contains a single
on local SSD, on an M2 Max MBP with 32GB of RAM running macOS 15.4.1 Hope that helps, it's end of day here now so I'm clocking off but feel free to ask for more info and I'll reply tomorrow. EDIT: just to add that I don't have any tailwind-specific config settings in my settings.json |
Not sure if this helps at all but when I go back to the working version of this extension (0.14.13) and then run "Tailwind CSS: Show Output" I can see that it does seem to try and parse quite a bit of stuff before it gets to the 'Preparing projects' & 'Adding watch patterns' step... there's around 80 entries along the lines of:
|
If there's that many then it's finding a lot of files that it considers config files.
Even in a project (in my testing) with a few hundred config files things are quick enough that it doesn't take 15s for the search to happen (the current limit). I set this because VSCode's file search can get stuck for long period when a project has lots of symlinks. Does your project have a bunch of those by chance? And I figured if the search is taking 15s+ there's very likely other problems going on. |
The vast majority of them (68) are actually .less files and are not in projects that use Tailwind. They all seem to have identical
The one thing I can see that I think seems to be common to these files is that they all have
Some but not a crazy amount
I can probably obfuscate the list enough for it to be safe to share
In my VSC settings.json I have - only set to exclude all |
Tailwind CSS: Show Output from 0.14.13
|
What does your code workspace file look like? Are you opening a folder and maybe a sub-folder of it? We currently don't try to de-duplicate work across workspace folders but that's something I've wanted to work toward for a while as just-in-case scenario — just need to find time to rip out and change a bunch of internal stuff. Aside: Seeing I don't see anything that jumps out at me as to why the search would time out though. Only thing I can think of is symlinks causing a slowdown but it'd be hard to believe its that much of one if 0.14.13 worked. Something you can try is setting this and seeing if it helps:
|
That seems to be the source of the problem! Somehow I'd managed to open another branch of the repo I was working on a while back as a folder in the same workspace?! Hadn't noticed because it was scrolled off the bottom of the Explorer view... Have removed that folder from the workspace and updated to Tailwind CSS Intellisense 0.14.5 - and it all seems to be working again now! |
😱 Now I'm really curious what the structure looked like. Would love to have a way to (maybe) detect or guard against this. Wild |
Not sure how much this will help but in the VSC Explorer view it would have been something like this:
|
Hmm yeah not sure then. Only guess I can make is that node_modules was being scanned inside Okay, thanks for the info! |
What version of VS Code are you using?
v1.98
What version of Tailwind CSS IntelliSense are you using?
v0.14.15, but now return to v0.14.13
What version of Tailwind CSS are you using?
v4.0.14
What package manager are you using?
npm
What operating system are you using?
Windows
Tailwind config
In new version we don't have tailwind.config.js
VS Code settings
Reproduction URL
I can't do this, it's a private repo
Describe your issue
After updating the Tailwind CSS IntelliSense extension to v0.14.14, IntelliSense stopped working completely in .php, .html files. No class name suggestions are provided.
I updated to v0.14.15, hoping it would resolve the issue, but the behavior remains the same.
Things I tried:
Confirmed that Tailwind CSS is working in the frontend (classes are being applied correctly)
The text was updated successfully, but these errors were encountered: