- What is BlatUI and how does it compare to shadcn/ui or Flux Pro?
- BlatUI is a copy-paste component library for the BLAT stack: Blade, Laravel, Alpine.js and Tailwind CSS v4. It ports the shadcn/ui design language and component APIs to Laravel, shipping 155 components, 614 variants, 64 blocks and 70 charts. Unlike Flux Pro, a CLI copies the source straight into your project, so you own the code and can edit it freely. It is positioned as a free, you-own-the-code alternative for Livewire apps.
- How do I install BlatUI in a Laravel application?
- Install the package with composer require anousss007/blatui, then run php artisan blatui:init to publish the theme tokens and JavaScript engine into resources/css and resources/js. You use php artisan blatui:add to copy individual components into resources/views/components/ui/, and the resolver pulls in any transitive component dependencies while printing required Composer and npm peers. Run blatui:init as a quick doctor check before writing UI so you can verify the setup. The whole path is designed to take about a day on a greenfield Laravel app.
- Does BlatUI work with Livewire?
- Yes. Every form control is Livewire-ready, including inputs, selects, checkboxes, switches, sliders, date and time pickers, and file uploads. wire:model two-way binding works out of the box on each of them. The docs include a dedicated Livewire guide covering how to register Alpine plugins via alpine:init when Livewire owns the Alpine instance.
- Which PHP, Laravel and Tailwind versions does BlatUI support?
- BlatUI requires PHP 8.2 or newer and Laravel 11, 12 or 13. It targets Tailwind CSS v4 and Alpine.js 3 as its styling and interactivity layers. If you are on an older Laravel release, you will need to upgrade the framework first, since those versions are not supported.
- Can I use BlatUI with Tailwind CSS v3?
- No. BlatUI depends on Tailwind v4-only features such as @theme inline and oklch design tokens, so a v3 app will not render the components correctly. You would need to run npx @tailwindcss/upgrade first, and that migration is a project in its own right because it can restyle arbitrary existing pages. Where you are already on v4 or starting greenfield, integration cost drops sharply.
- Are BlatUI components accessible and WCAG AA compliant?
- Accessibility ships in every component: WAI-ARIA roles, complete keyboard navigation and focus management, and WCAG AA color contrast. The behavior is modeled on shadcn/ui's Base UI components, verified in a real browser and audited with axe-core. Because the source is copied into your project, you can also inspect and adjust markup directly for your own accessibility governance reviews.
- Will updating BlatUI overwrite the components I have customized?
- No. Components live in your project rather than vendor/, so composer update never overwrites your edits. The blatui:update command cannot tell your customizations apart from a stale copy, so it prompts you file by file instead of patching blindly. That is safe by design, but treat upgrades as a real work item and track upstream releases yourself since there is no CVE or patch feed for copied source.
- How does BlatUI handle Alpine.js if my app already boots Alpine or uses Livewire Flux?
- Do not import blatui.js when your app already boots Alpine, or you will double-boot it and components will misbehave. With Livewire or Flux, Livewire owns the Alpine instance, so you register via the alpine:init event and install any plugins only. When coexisting with Flux Pro, also set darkMode: false to avoid two competing .dark togglers.
- Are the 64 blocks and 70 charts included in the Composer package?
- No. Components ship inside the package, but blocks and charts are fetched over HTTP from blatui.remix-it.com when you add them. That makes their availability a third-party dependency and an air-gap blocker for regulated or offline environments. If you need self-contained installs, audit this before standardizing on BlatUI.
- Is BlatUI MIT licensed and safe for commercial use?
- The README and Packagist both state MIT, but GitHub currently reports the repository license as NOASSERTION, so confirm with legal before commercial deployment rather than trusting a badge. Also weigh the maintenance profile: a single-author monorepo with roughly 262 stars and no dependents means no community backpressure on bugs. Plan to own security triage and upgrade diffing for the copied components yourself.