- How do I install BlatUI in a Laravel application?
- Install it with composer require anousss007/blatui, add the two peer packages, then run npm install. After that run vendor:publish, add the BlatUI import to app.css and app.js, and finish with php artisan blatui:init, which acts as a doctor command that verifies the setup. On a fresh Laravel app already running Tailwind CSS v4 the whole integration is essentially two file edits plus the publish step.
- Which Laravel, PHP and Tailwind CSS versions does BlatUI support?
- BlatUI requires PHP 8.2 or newer and Laravel 11, 12 or 13. Tailwind CSS v4 is mandatory because the components rely on v4 features such as @theme inline and oklch color tokens. Teams still on Tailwind v3 must run the npx @tailwindcss/upgrade migration first, which is a separate project with its own blast radius rather than a subtask.
- Is BlatUI compatible with Livewire?
- The README describes BlatUI as Livewire-ready, with wire:model two-way binding on every form control including inputs, selects, checkboxes, switches, sliders, date and time pickers and file uploads. That positions it as a free, you-own-the-code alternative to Flux Pro. However, Livewire-specific documentation is a notable gap for a Laravel package and there is no public evidence of the combination working at scale, so spike it before committing.
- Will BlatUI break my existing Alpine.js or Livewire setup?
- It can. If your app already runs Alpine, which is the default for Livewire applications, importing blatui.js may boot a second Alpine instance and silently break both. A registerBlatUI(Alpine) path exists for passing in your existing instance, but combining it with Livewire's bundled Alpine plus the anchor, collapse and focus plugins is an untested-in-public combination. Test this first, because it is the single biggest feasibility unknown.
- Does updating BlatUI overwrite the component files I have edited?
- The README states that updates never overwrite your edits, but the changelog repeatedly instructs users to re-run blatui:add to pick up fixes, and that command writes files. There is no documented diff, manifest or three-way merge, so no one can say for certain what happens to a locally modified component. Verify it empirically on a patched component before relying on either claim, especially before applying security or accessibility fixes.
- Can I use BlatUI with Inertia.js, React or Vue?
- No. BlatUI is Blade-first and server-rendered with Alpine.js providing interactivity, so there is no React or Vue runtime and no hydration or client-side rendering model. It is a strong architectural match for a conventional Laravel monolith and a poor match for SPA-first front ends, API-only services, or teams whose design system already lives in a JavaScript component library.
- How does BlatUI compare to shadcn/ui and Flux Pro?
- BlatUI is a port of shadcn/ui to the BLAT stack of Blade, Laravel, Alpine and Tailwind, keeping the same design language, component APIs and blocks. Like shadcn/ui it copies components into your project instead of resolving them from vendor, so you own, can patch and can fork the source. Against Flux Pro it is free and not tied to a paid license, but it has no comparable production track record and a less documented Livewire story.
- How many components does BlatUI include and are they accessible?
- BlatUI ships 155 components with 614 variants, plus 64 blocks and 70 charts. Accessibility is a headline claim: WAI-ARIA roles, complete keyboard navigation and focus management, and WCAG AA color contrast, verified in a real browser and audited with axe-core. Expect some unevenness in per-component depth given that 75 components were added in a single minor release.
- Will BlatUI's components clash with my own x-ui Blade components?
- Yes, if you already use the x-ui prefix. BlatUI installs into the fixed resources/views/components/ui directory using the x-ui.* namespace, so an application with its own x-ui.* components will conflict. Audit your existing component directory before installing, or plan a rename pass.
- Is BlatUI MIT licensed and safe to use in a commercial project?
- The README claims MIT, but Composer reports the license as NOASSERTION, and the set is a port of shadcn/ui that also bundles Lucide icons and ApexCharts, which creates layered attribution obligations. Treat legal sign-off as a gate rather than a checkbox and confirm the license on Packagist and in the LICENSE file. Also weigh maturity: one maintainer, roughly 260 stars, zero dependents, a recent package rename and no public production evidence yet.