- How do I install maryUI in a Laravel Livewire project?
- Install via Composer with `composer require robsontenorio/mary`. Ensure Tailwind CSS is already configured in your project, as maryUI relies on it. Run `npm install` and `npm run dev` to compile Tailwind with DaisyUI included. No additional Livewire setup is needed beyond the package’s dependencies.
- Does maryUI work with Laravel 10 or 11?
- Yes, maryUI is fully compatible with Laravel 10 and 11, as it supports Livewire 4, which is the default in these versions. Check the [official documentation](https://mary-ui.com) for version-specific notes if you’re using an older Laravel release.
- Can I use maryUI without Livewire?
- No, maryUI is designed exclusively for Livewire projects. If your Laravel app doesn’t use Livewire, you’ll need to migrate to it first or explore alternatives like Tailwind UI or PrimeVue for non-Livewire setups.
- What if my project uses Bootstrap instead of Tailwind?
- maryUI requires Tailwind CSS and DaisyUI, so switching frameworks would be necessary. Evaluate the effort to migrate from Bootstrap to Tailwind, including updating CSS classes and rebuilding components. For small projects, the trade-off may not be worth it.
- Are there breaking changes when upgrading maryUI?
- Yes, recent versions (e.g., v2.7.0+) introduced breaking changes like upgrades to VanillaCalendarPro v3 and refactored JavaScript dependencies. Always review the [changelog](https://github.com/robsontenorio/mary/releases) and test components in a staging environment before upgrading.
- How do I customize maryUI’s DaisyUI theme?
- Extend or override DaisyUI themes in your `tailwind.config.js` by adding the DaisyUI plugin and configuring themes. Example: `plugins: [require('daisyui')], daisyui: { themes: ['light', 'dark', 'cupcake'] }`. This allows you to match your project’s design system while keeping maryUI’s components intact.
- Does maryUI add significant JavaScript bundle size?
- Some components (e.g., Calendar, Choices) include third-party JS dependencies like vanilla-calendar-pro or flatpickr, which can increase bundle size. Audit your project’s build output with tools like Webpack Bundle Analyzer to assess the impact before full adoption.
- Can I use maryUI components alongside existing Blade templates?
- Yes, maryUI components are Blade-compatible and can be mixed with existing templates. Use them like any other Blade directive, e.g., `@maryButton('Submit', 'primary')`. No refactoring is required for non-Livewire Blade views.
- What’s the best way to test maryUI before full adoption?
- Start with non-critical components like buttons, cards, or toasts to validate integration. Example: `@maryToast('Success!', 'success')`. Monitor performance, theming consistency, and developer experience. Gradually replace legacy components once confidence is established.
- Are there alternatives to maryUI for Laravel Livewire?
- If you’re using Livewire, alternatives include Tailwind UI (customizable but not Livewire-specific), PrimeVue (Vue-based), or Laravel Nova (for admin panels). For Tailwind-focused Livewire projects, maryUI stands out for its polished, ready-to-use components with minimal setup.