I agree with you. But I think this is a symptom of a different problem: Building admin panels with UI tools instead of config-driven tools. While component lib

I agree with you. But I think this is a symptom of a different problem: Building admin panels with UI tools instead of config-driven tools. While component libs like this can be used for consumer-facing UI, when we talk about "dashboards" it's also often backoffice admin panels. You shouldn't be reaching for hand-writing UI design & logic in that scenario. You should be looking for an admin panel interface tool. Laravel has these in spades: Nova, Backpack, and Filament are the big three. You write some code and some logic tied to it, and the tool creates the UI for you. This lets you get back to writing code for the actual customers instead of for business processes. These can be used for consumer facing panels too, but with less control over the design, they're not really intended for it. But the JS ecosystem insists on being fragmented, so everything is rewritten manually. "Batteries included" needs a lot more than just batteries (the UI components).