- How do I install maryUI in a Laravel application?
- Install it with Composer using composer require robsontenorio/mary, then run the package installer and publish its config. You must add mary's vendor views to your Tailwind content globs, register daisyUI in tailwind.config.js, and choose a daisyUI theme. With Livewire and Vite already in place, a working page is typically achievable within a day.
- Which Laravel versions does maryUI support?
- maryUI is a Blade component library for Livewire, so your Laravel version is largely irrelevant. The real compatibility contract is your Livewire major version plus your Tailwind and daisyUI versions. Confirm that the current maryUI branch is validated against the Livewire major you run before adopting it.
- Does maryUI work with Tailwind CSS v4 and daisyUI v5?
- You need to verify this against your own build, because maryUI couples to daisyUI and Tailwind rather than to Laravel internals. Since version 1.41.6 the installer locks dependency versions, which helps reproducibility but may pin you to a daisyUI and Tailwind combination you did not choose. Check that pinned combination against your existing front-end build before rollout.
- Can I use maryUI alongside Filament or another Blade component kit?
- It is technically possible but not recommended. Mixing two component kits produces divergent form semantics, validation display, and theme tokens. If you already standardize on Filament or another Blade kit, maryUI is a poor fit for the same surfaces.
- Does maryUI work with Inertia, Vue, or React front ends?
- No, maryUI is Livewire-first and its components compile to Blade and HTML that interact through wire:model and Alpine directives. It is a poor fit if your product surface is Inertia, Vue, or React. It is a strong fit if your admin or back-office UI is Livewire-based and currently hand-rolled.
- What license does maryUI use, and are there licensing risks?
- The README and license.md state MIT, though Packagist reports NOASSERTION, so have legal confirm the LICENSE file text before shipping it in a distributed product. Separately, the Editor component wraps TinyMCE, which carries GPL implications; the package added a gpl-license attribute in 1.41.2 for this reason. Do not ship the Editor component without a licensing decision.
- Are maryUI minor version upgrades safe, or can they break my UI?
- Treat any minor bump as potentially breaking and pin the package exactly. Version 2.3.0 renamed enabled to hidden on Menu, MenuItem, and MenuSub inside a minor release, and 2.0.0 required a dedicated upgrade guide. Recent patches have also included small UI regressions such as Tab badge prefixes and Drawer ids.
- How do I customize maryUI components and theming?
- Components are customizable through standard Tailwind utility classes, and theming is handled by daisyUI themes. If you already have a Tailwind palette or brand design system, either map daisyUI themes onto your tokens or accept two parallel systems. Per-component customization is supported, but plan for the token mapping work up front.
- Which maryUI components add JavaScript weight and accessibility risk?
- Risk concentrates in components that ship third-party JavaScript: Editor (TinyMCE), Choices and ChoicesOffline, Datepicker, Signature, File and ImageLibrary (cropper), and Carousel. Each adds bundle weight, its own accessibility behavior, and its own upgrade cadence. Inventory which components you actually need versus nice-to-have before committing to the full set, and have accessibility sign-off cover modal focus trapping, RTL support, and keyboard navigation in Choices.
- Is maryUI actively maintained and safe for production use?
- It is actively maintained with frequent patch releases, clear docs, a Discord community, and roughly 1.5k GitHub stars. However, it is a single-maintainer, sponsor-funded dependency, and the reported dependent count is zero, so public war stories for edge cases are thin. Pin exact versions, audit accessibility on the components you use, and set a policy for sponsor-funded UI-layer dependencies before production adoption.