- What Laravel and Livewire versions does LaraLiveUI support?
- LaraLiveUI requires **Laravel 10.0+** and **Livewire 3.5.19+** for full compatibility. Older versions may work but aren’t officially tested, and Tailwind CSS v4 is mandatory for styling.
- How do I install and set up LaraLiveUI in my Laravel project?
- Run `composer require elnasnato/laraliveui`, add `@laraliveuiAppearance` in your `<head>` and `@laraliveuiScripts` before `@livewireScripts` in your `<body>`, then import the CSS in `app.css`. No manual configuration is needed beyond these steps.
- Can I customize the styling of LaraLiveUI components without modifying the package?
- Yes, LaraLiveUI supports **Tailwind CSS customization** via your `tailwind.config.js`. Override colors, spacing, or variants by extending the imported `laraliveui.css` in your own CSS file. No design token system is documented yet, but Tailwind’s utility classes work as expected.
- Are LaraLiveUI components accessible (WCAG-compliant) out of the box?
- The package follows **Tailwind and Livewire best practices** for accessibility, including ARIA attributes where applicable. However, since it’s a new project, test components thoroughly for edge cases like keyboard navigation or screen reader compatibility.
- What’s the difference between LaraLiveUI and FluxUI/SheafUI? Should I migrate?
- LaraLiveUI **borrows conventions from FluxUI** (e.g., `data-laraliveui-*` attributes) but uses its own `laraliveui:` prefix. If you’re using FluxUI, migration is straightforward—just replace `flux:` with `laraliveui:`. SheafUI users may face inconsistencies due to differing design patterns.
- Does LaraLiveUI support dark mode? How is it persisted across pages?
- Dark mode is supported via Tailwind’s `dark:` variant. The package **does not document server-side persistence**, but client-side persistence (e.g., `localStorage` or cookies) can be added manually using Alpine.js or Livewire’s session management.
- Are the ‘pro’ components (from FluxUI) included in the MIT license, or do they require separate licensing?
- The **README does not clarify licensing for pro components**. Since the package is MIT-licensed, assume free components are covered, but verify FluxUI’s pro terms separately. Commercial use may require additional agreements—check the [documentation](https://elnasnato.github.io/laraliveui-docs/) for updates.
- How does LaraLiveUI handle performance? Can I lazy-load components or assets?
- LaraLiveUI **does not document lazy-loading** for components or assets. The JS/CSS bundle is optimized for Tailwind, but manual lazy-loading (e.g., Alpine.js or dynamic imports) can be implemented. Test bundle size against alternatives like SheafUI (~10–20KB for core components).
- What if I encounter bugs or need support? Is there a community or roadmap?
- With **0 stars and no active community**, support relies on GitHub issues. The project lists a **2026 release date**, suggesting early-stage development. Monitor the [repo](https://github.com/elnasnato/laraliveui) or documentation for updates—no official roadmap exists yet.
- Can I use LaraLiveUI with Livewire’s latest features (e.g., reactivity system, Alpine 3.x)?
- Yes, LaraLiveUI is **built for Livewire 3.5.19+**, which includes Alpine 3.x integration. The package leverages Alpine for interactivity, so it should work with Livewire’s latest reactivity features. Test thoroughly for edge cases like nested components.