- Is hawkiq/hwkui compatible with Laravel and Livewire 3?
- Yes. HWKUI is a Blade-component UI kit built for Laravel Livewire 3+ and is aimed at admin panels and dashboards. It fits best in a conventional Laravel monolith that already uses Blade, Livewire, Tailwind, and Alpine. It is a poor fit for Inertia, Vue, or API-first frontends.
- How do I install hawkiq/hwkui in a Laravel application?
- Install it with Composer using composer require hawkiq/hwkui, then publish the package config, views, and assets. Register the vendor component paths in your Tailwind content configuration and rebuild your CSS. Confirm Alpine is loaded exactly once before rendering components.
- How do I publish HWKUI views, config, and assets?
- First-time adoption is expected to require publishing config, views, and assets, typically through the package's publish command. After publishing, register the vendor directory in your Tailwind content paths so component classes are generated. Clear compiled Blade views and rebuild assets after publishing or upgrading.
- Do I need Alpine.js for hawkiq/hwkui components?
- HWKUI components use Alpine-style client-side directives for interactivity, so an Alpine setup is expected. The provided materials do not confirm whether Alpine is bundled or assumed present. Verify your layout loads Alpine exactly once, because double registration is a common failure for this type of package.
- Does HWKUI support Livewire wire:navigate SPA mode?
- Livewire 3's wire:navigate SPA mode is part of the supported architecture, and version 1.1.3 fixed a Tour widget bug that appeared under wire:navigate. Still test tour step indices, open and closed state, and portal containers after navigation. Bugs in this class can recur when Livewire swaps the DOM.
- Does hawkiq/hwkui support Livewire 2?
- The package is described as a widgets library for Laravel Livewire 3+, and the evaluation only confirms Livewire 3 assumptions. There is no evidence of Livewire 2 support. Check the composer.json constraints before attempting an older Livewire install.
- Can I use hawkiq/hwkui with Inertia, Vue, or an API-first frontend?
- No. HWKUI ships Blade components and Livewire-oriented widgets, so components would be dead weight in an Inertia, Vue, or API-first app. It is intended for Blade-rendered Laravel applications that already use Livewire and Tailwind.
- Is HWKUI accessible for tours and keyboard navigation?
- The evaluation flags focus trapping, ARIA labelling, Escape-to-dismiss, and keyboard navigation as open questions for onboarding overlays such as the Tour widget. Do not assume full accessibility without testing the specific components you use. Run an accessibility audit before shipping tours or overlays to production.
- Does HWKUI support dark mode, RTL, and design tokens?
- Version 1.1.3 exposes widget options for text and next-button colors, which is inline theming rather than design-token theming. The materials do not mention automatic dark-mode or RTL handling for those values. Wrap components in local Blade components if you need consistent tokens and control over per-instance overrides.
- Is hawkiq/hwkui actively maintained and production ready?
- It is a single-organization GitHub project with a short release cadence, and the evaluation finds no security policy, LTS branch, or multi-maintainer bus factor. There is also no evidence of a Livewire test suite that exercises wire:navigate transitions. Pin versions, read changelogs, isolate it behind your own Blade wrappers, and treat it as a vendor-lite dependency.