Hello Folks,
We’re working on a Phoenix 1.8.1 new codebase, and loving to have the native DaisyUI component library available that comes out of the box with it.
But with Phoenix 1.8 came along an issue that was vscode’s Intellisense extension not suggesting anymore the classes names that it does at Phoenix 1.7.x codebases.
As for the TailwindCSS classes names, we managed to solve it by creating a blank assets/tailwind.config.css file, that, just by existing, seems to have made Intellisense aware that there’s TailwindCSS around here. 
But as for the DaisyUI classes names, we still can’t find the solution to make Intellisense suggest them. The only options that it gives are the TailwindCSS native classes. And it would be awesome to see there also the DaisyUI component classes.
Did anyone run into this and could share the approach to get it working?
Thanks a lot, folks!
André
Thanks a lot for the reply, rhcarvalho.
Precisely, that makes total sense.
As for the issue, I was wondering if there’s any workaround we can do, like building a bit more of the file infra and content that Intellisense can understand.
For example: by creating the file assets/tailwind.config.css we already have the TailwindCSS classes working on IntelliSense. So I am wondering what could we do to make it understand-and-suggest DaisyUI classes.
Any ideas on that?
Thanks a lot in advance!
Unfortunately, no idea. I haven’t had the time to embark on Tailwind v4 and DaisyUI yet… And this type of issue is no incentive to accelerate that move
Can’t live on the bleeding edge without bleeding! 
1 Like
Not sure if it helps but adding this settings to vscode json fixed it for me:
{ "tailwindCSS.experimental.configFile": "assets/css/app.css" }
Or to the path of your CSS file that handles the @import tailwindcss and @import daisyui
Hey SyahmiRafsan, thanks for the contribution.
The path at Phoenix 1.8.1 seems to be exactly this one you posted, but adding this to settings.json didn’t get it working here. Intellisense TailwindCSS suggestions just don’t show up. Not even after restarting vscode.
The only thing that really works is adding the empty assets/tailwind.config.js file, as I mentioned above. And even this only gets the TailwindCSS native classes working, and not the daisyUI classes.
Any other ideas, Phoenix fellows?
I see. Can you please share whats the Tailwind Intellisense output from the output → Tailwind?
It should mention any issues ie mistakenly detecting Tailwind V3 and not the default Tailwind V4 from Phoenix 1.8.1.
Also do check if you are on the latest Tailwind VSCode extension too, in case there are updates already to fix this.
I’m having the same issue with Phoenix 1.8.1, VSCode 1.105.1 and plugin version 0.14.28
