Level 13
Have you added the css asset to your blade file?
Just to test something out... Try if the autocomplete works in the dashboard.blade.php file...
Dec 29, 2021
8
Level 4
Tailwin 3.0 and autocomplete
Goodmorning,
I just started a new project and installed tailwind, based on 'https://tailwindcss.com/docs/guides/laravel'
After I ran RUN NPM DEV (or RUN MPM Watch), the classes will become available in PHP STORM and I can use it during auto completion. But classes which I did not used yet, are not yet available in the autocompletion option.
I never experience this with the previous versions of tailwind, and it make sence because (afaik) the JIT engine..
My question is, what should be the workflow to use Tailwind 3.0 and have my EDI recognize all possible classes and not one the one I already used?
Hope someone has some tips..
Level 4
Yes I have..
What happens.. I write something like class="bg-red-400", Then nothing happens, but after NPM RUN DEV, the next time if I use "bg-r ..... " the autocompletion works. So it is recognized..
I tested it on welcome.blade.php as well and same behavior. :-(
Level 102
Are you sure you have the latest plugin version? Go to Help->Check for updates
Level 4
Yes, I just ran an update to 2021.2.4 and the plugins are updated.. Next to this, I ran Diagnostictools -> indexing as well. (maybe not needed, but anyway).
Level 50
It's a known issue. See https://youtrack.jetbrains.com/issue/WEB-52736 https://youtrack.jetbrains.com/issue/WEB-53365
Level 4
Thanks for pointing out to jetbrains.. Unfortunately my issues is not exactly the same, but might of course have the same rootcause.. I even don't get css classes suggestions. In your example you see font- and the possible options. If I do font-, there is nothing, except the classes I already used and after my npm run... And only those.. :-(
Level 102
@esorone why not create a ticket with jetbrains support? They can perhaps tell you if it the same issue
Level 4
@sinnbeck Never thought about that one.. I will create a ticket!... Next to this I will try to see if I can create a kind of workaround.. full css file on version 3 or something.
Please or to participate in this conversation.