Tailwind class "!" prefix removed when using Panel from custom package

Hello! I've created a Laravel package and a panel provider inside. Everything works just fine however I have a strange issue with tailwind. It does not matter whether I add custom vite theme to the panel or just use a default theme. There is a !max-w-[14rem] class in dropdown by default. I can see this class in css output generated by Filament and also in my custom theme. But when I load a panel from my package, the ! prefix is gone in html! When I have a fresh Laravel app with filament inside, the prefix is there. Any ideas what could I check to debug it?
No description
No description
11 Replies
Krzysztof
KrzysztofOP4mo ago
The first screenshot is from my custom package, the second is a fresh Laravel app with filament When I search vendor folder for the class, I only get this one occurrance:
null => '!max-w-[14rem]',
null => '!max-w-[14rem]',
inside dropdown/index.php There is nothing without the ! Could it be some Tailwind configuration that strips the ! from classes? 🤔
LeandroFerreira
LeandroFerreira4mo ago
same filament version?
Krzysztof
KrzysztofOP4mo ago
yep but will try updating to double check v3.2.97 in composer.lock for both
LeandroFerreira
LeandroFerreira4mo ago
php artisan filament:assets to copy the assets again?
Krzysztof
KrzysztofOP4mo ago
did not help, but I've notice the difference in assets cache tag, the fresh Laravel app loads http://filament.test/css/filament/filament/app.css?v=3.2.97.0 whis is the right version, but the package loads http://workflou.test/css/filament/filament/app.css?v=3.2.40.0. The 3.2.40 matches filament/actions package version (in both cases) But filament/filament package and filament/support are on 3.2.97 don't know it that can cause issues though, probably just a cache bump clearing cache does not help
LeandroFerreira
LeandroFerreira4mo ago
try php artisan filament:clear-cached-components
Krzysztof
KrzysztofOP4mo ago
no changes, also I did not use php artisan filament:cache-components so it should not matter?
LeandroFerreira
LeandroFerreira4mo ago
ok just to check if it was a view cache..
Krzysztof
KrzysztofOP4mo ago
I think I found the issue, somehow Laravel decided to install the older version of filament. So the assets are fresh but the html comes from before 5 months (when the ! was introduced). Will post an update when I'll find the cause of my stupidity 🙂
LeandroFerreira
LeandroFerreira4mo ago
Yes, I believe this issue is related to your project, because it doesn’t make sense that Tailwind is stripping the ! No problem 👍
Krzysztof
KrzysztofOP4mo ago
thanks for help! as I stated before it was some versioning issue. Even though the composer.lock had the right version, the old version of filament has been installed in vendor folder. I've removed vendor, reinstalled with composer and had to also remove storage/framework/views cache and it's working
Want results from more Discord servers?
Add your server