Laravel ecosystem updates: DaisyBlade release and Alpine.js conflict solutions

New developments and troubleshooting guides have emerged within the Laravel ecosystem regarding UI component stacks and library conflicts.

edumicro has released DaisyBlade, a package designed for Laravel ERP and CRM interfaces. The library utilizes a stack consisting of Blade, Alpine.js, and DaisyUI. Unlike previous iterations, this version is rebuilt without Livewire, opting for a philosophy of explicit server calls via Axios and plain Laravel controllers returning JSON to avoid protocol overhead.

Separately, developers using Livewire 3 with the Laravel Breeze starter kit have reported reactivity issues and console errors. These errors, such as ‘Uncaught TypeError: window.Alpine.cloneNode is not a function’, are caused by Alpine.js being loaded twice—once by Breeze and once built into Livewire. The recommended solution involves removing the manual Alpine.js initialization from the Breeze assets and adding @livewireStyles and @livewireScripts to the application layout.