- What Laravel and Livewire versions does maryUI support?
- maryUI is actively maintained for Laravel 10/11 and Livewire 4+. It also supports Laravel 9 and Livewire 3, but some newer features (e.g., VanillaCalendarPro v3) may require testing. Always check the [official docs](https://mary-ui.com) for version-specific notes.
- Do I need Tailwind CSS or daisyUI already configured to use maryUI?
- Yes, maryUI requires Tailwind CSS (v3+) and daisyUI to be pre-configured in your project. If you don’t have them set up, you’ll need to install and configure them first, which may add initial setup time. The package won’t work without these dependencies.
- Can I use maryUI in a Laravel app without Livewire?
- No, maryUI is designed exclusively for Livewire-powered Laravel applications. If your project uses Inertia.js, Vue, React, or vanilla Blade, this package won’t integrate natively. Consider alternatives like standalone Tailwind components or Alpine.js for non-Livewire setups.
- How do I install maryUI in my Laravel project?
- Install via Composer with `composer require robsontenorio/mary`. Ensure Tailwind and daisyUI are already configured in your project. No additional build steps are required for basic usage, though customization may involve Tailwind configuration. Follow the [installation guide](https://mary-ui.com/docs/installation) for details.
- Are there breaking changes when upgrading maryUI?
- Yes, recent versions (e.g., 2.7.0+) introduced breaking changes like the migration to VanillaCalendarPro v3 and refactoring of currency.js. Always review the [changelog](https://github.com/robsontenorio/mary/releases) and test upgrades in a staging environment to avoid runtime issues.
- Does maryUI work with CDN-loaded assets like VanillaCalendarPro?
- Yes, critical dependencies like VanillaCalendarPro can be loaded via CDN to reduce bundle size. However, CDN-loaded assets may bypass cache invalidation in some deployment pipelines, so test thoroughly in production to ensure consistent behavior across environments.
- How customizable are maryUI’s components?
- maryUI components are built with Tailwind and daisyUI, offering extensive customization via Tailwind’s utility classes. However, heavy overrides (e.g., DaisyUI theme changes) may require deep Tailwind knowledge or additional CSS. Start with the [theming docs](https://mary-ui.com/docs/theming) for guidance.
- What if my project already has custom UI components (e.g., tables, modals)?
- Assess duplication risk before adopting maryUI. If your existing components align with maryUI’s design system, migration may be straightforward. Otherwise, you might need to refactor or extend maryUI’s components. Audit your current UI stack first to plan the transition.
- Is maryUI suitable for right-to-left (RTL) language support?
- maryUI includes recent RTL fixes for components like tables and dropdowns, but edge cases may still exist. Test thoroughly in your target RTL environment. The package leverages Tailwind’s RTL utilities, so ensure your Tailwind config supports RTL if needed.
- What alternatives exist if maryUI doesn’t fit my project?
- For Laravel + Livewire, consider standalone Tailwind components (e.g., [Tailwind UI](https://tailwindui.com/)), Alpine.js for lightweight interactivity, or frameworks like Inertia.js for SPA-like experiences. If you’re not using Livewire, explore Blade-based component libraries or Vue/React integrations.