Closed RyanPaiva56 closed 3 weeks ago
Check this issue already posted something related #489
@pirlo17 It wasn't that, but I did need to run npm run build
and then it ran perfectly, so the issue isn't any of the Flux code, but I'll leave this here in case Caleb wants to add something to the install steps. Is this something folks know by convention? I'm switching to Laravel TALL monolith from Laravel/NextJS and I didn't think I would need to be running a watch/build command. Maybe tailwind is only building the used css/js and that's why it didn't load until I rebuilt.
I'm going to go read some docs and see if I'm missing a chunk of how this dev flow is supposed to go. Caleb, does it make sense to add a "workflow" guide or a quick paragraph to the install guide?
I'm on Chrome. When I go to this page: https://fluxui.dev/layouts/header, the demo in full screen works perfectly:
https://github.com/user-attachments/assets/1d9ea3af-c220-466f-a5b9-44ce0b66c73d
And then if I copy and paste the code into a fresh copy of Laravel Breeze (Livewire), it does this:
https://github.com/user-attachments/assets/570aa36f-156f-40c2-95e4-279a1a5a0002
I followed all of the install steps. Here's my head code:
And at the bottom:
Tailwind config:
Here's the whole page of code: