- What is the lianmaymesi/wireblade package used for?
- WireBlade is a Laravel package that ships a Plain Admin-style UI built with Tailwind CSS and Alpine.js, packaged as reusable Blade components and utilities. It is aimed at developers building interactive, component-driven admin interfaces for Laravel and Livewire without hand-writing the same markup and boilerplate on every project. Because it lives in the Blade and Livewire view layer, it does not touch your domain or persistence code.
- How do I install WireBlade in a Laravel application?
- Install it with Composer using composer require lianmaymesi/wireblade, and the service provider should be picked up automatically through Laravel package discovery. If the package ships publishable configuration, views, or compiled assets, run php artisan vendor:publish for the relevant tag. Make sure your front-end build (Tailwind and Alpine via Vite or Mix) is compiling the package's view paths before you expect the components to render correctly.
- Which Laravel, PHP, and Livewire versions does WireBlade support?
- Check the require block in the package's composer.json before installing rather than discovering constraints from a failed dependency resolve. Confirm the declared ranges for php, illuminate/support or laravel/framework, and livewire/livewire all match your runtime matrix. The Livewire axis is the highest-variance item, so verify that major version explicitly if you plan to use the Livewire-facing components rather than plain Blade usage.
- Do I need Livewire to use WireBlade, or does it work with plain Blade?
- WireBlade's components are Blade components, so simple presentation pieces can often be rendered in a normal Blade view without any Livewire component wrapping them. The interactive, reactive parts rely on Livewire lifecycle behaviour and Alpine.js, so those surfaces need Livewire installed and configured. If you only need static admin layout and styling, Blade-only usage carries materially less upgrade risk.
- Is WireBlade compatible with Livewire 3?
- That depends on the version constraints the package declares, so verify them in composer.json rather than assuming compatibility. A package written against Livewire 2 may install and load under Livewire 3 yet misbehave in lifecycle hooks, component resolution, or asset injection. Test the specific components you use on your Livewire major version, and prefer a Blade-only usage pattern if you cannot confirm support.
- Can I customize the WireBlade admin UI with my own Tailwind theme?
- Yes, in practice you customize it the same way as any Tailwind-based component library: adjust your tailwind.config.js content paths and theme tokens, and override the component views or classes you want to change. Because the markup is Blade you can publish the views and edit them directly instead of fighting a compiled CSS bundle. Keep your overrides in your own files where possible so package updates do not silently overwrite them.
- Should I run vendor:publish after installing or upgrading WireBlade?
- Run vendor:publish only when you deliberately want to override the package's config, views, or assets, and use the specific tag rather than publishing everything. On upgrade, diff the newly published files against the copies already in your application instead of blindly re-publishing. Silent config and view overwrites are the most common self-inflicted incident with this class of package.
- How do I safely upgrade WireBlade from 2.3 to 2.3.1?
- Read the diff between the two tags first and classify the changes as cosmetic, dependency-only, or behavioural, because a patch bump is a semver promise rather than a guarantee. Then pin the exact version (2.3.1) in a branch, run composer update lianmaymesi/wireblade --with-dependencies, and inspect the lockfile delta to see if any transitive packages also moved. Run your test suite plus any snapshot or visual tests covering the affected views, then smoke-test on staging with production-like asset compilation before rolling out with a rollback pin ready.
- Is WireBlade production-ready, and how does it compare to Filament or Orchid?
- WireBlade is a lightweight UI component layer rather than a full admin panel generator, so it is closer to a styled component kit than to Filament or Orchid, which provide resource scaffolding, forms, tables, and authorization out of the box. That makes it a reasonable fit when you want a Plain Admin look with your own controllers and Livewire components, and a poor fit if you want generated CRUD screens. Note that it is a small-maintainer package, so review release diffs, pin exact versions, and check issue responsiveness before relying on it in production.
- How do I test Laravel views and Livewire components built with WireBlade?
- Test the Blade components you compose with standard Laravel view or component assertions, and use Livewire's testing helpers for any reactive behaviour that depends on lifecycle hooks. Add a few snapshot or visual tests around the admin surfaces you actually use, since UI packages tend to break in markup rather than in exceptions. Run these on every dependency bump, and confirm the package's own test suite and CI ran against the tag you are installing.