I dnt like tailwind css coz it have many class . in bootstrap we use 2 or 3 class but in tailwind we need to use 20 - 30 class . It make file un readable
if tailwind can catch changes and auto include new classes automatic on the fly like JIT mode, i might try it again, every change need to recompile can be difficult sometime.
When working on a heavy duty page ( lots of elements to load and with slow data sets ) it gets superbly slow and doesn't really help when all you want is to beautify it@@LaravelDaily When working on lightweight pages is it amazing
I thought this was standard behaviour when using tailwind with laravel? Eg 2 terminals one for artisan serve and one for npm run Dev/watch. It also refreshes the view and or CSS on page automatically if you use :3000 instead of 8000...
Hi there! Thanks for your useful content even for old-school experienced developers. I had an issue with tailwind compilation when I use a css class that is attributed programmatically through a php variable, and that class is not used anywhere else on the project. In this case the compilation does not discovery the class because it is not in a blade file. As workaround I created a dummy blade file to put those classes. Is there another solution for this cases? Thnaks!!
@@LaravelDaily Thank you, I appreciate the quick reply. 💪 Actually, I saw this suggestion to define new custom attributes. I will investigate where I should define that config (may in tailwind.config file? 🤔) I think that maintaining a blade file sounds an easy way to solve this. I know it sounds like an anti-pattern. What do you think guys? Thoughts, concerns?? Let me know.
![Cody Johnson - I'm Gonna Love You (with Carrie Underwood) [Official Music Video]](http://i.ytimg.com/vi/yy9PuYMU29g/mqdefault.jpg)
I would be very glad if you took the time to describe how the tailwind compilation works, when I use vue and vite in Laravel.
I did explain it in the course, in a few lessons: not specifically related to Vue but the logic is the same with or without Vue.
@@LaravelDaily Thank you a lot!
I dnt like tailwind css coz it have many class . in bootstrap we use 2 or 3 class but in tailwind we need to use 20 - 30 class . It make file un readable
if tailwind can catch changes and auto include new classes automatic on the fly like JIT mode, i might try it again, every change need to recompile can be difficult sometime.
Npm run dev with Vite should do what you're saying
When working on a heavy duty page ( lots of elements to load and with slow data sets ) it gets superbly slow and doesn't really help when all you want is to beautify it@@LaravelDaily
When working on lightweight pages is it amazing
There is also a jit setting, which you can activate. Just search for it.
In most cases, it is not necessary.
I thought this was standard behaviour when using tailwind with laravel? Eg 2 terminals one for artisan serve and one for npm run Dev/watch. It also refreshes the view and or CSS on page automatically if you use :3000 instead of 8000...
Hi there! Thanks for your useful content even for old-school experienced developers.
I had an issue with tailwind compilation when I use a css class that is attributed programmatically through a php variable, and that class is not used anywhere else on the project. In this case the compilation does not discovery the class because it is not in a blade file. As workaround I created a dummy blade file to put those classes. Is there another solution for this cases?
Thnaks!!
I googled and found some answers here: stackoverflow.com/questions/69687530/dynamically-build-classnames-in-tailwindcss
@@LaravelDaily Thank you, I appreciate the quick reply. 💪
Actually, I saw this suggestion to define new custom attributes. I will investigate where I should define that config (may in tailwind.config file? 🤔)
I think that maintaining a blade file sounds an easy way to solve this. I know it sounds like an anti-pattern. What do you think guys? Thoughts, concerns?? Let me know.