- How do I install and register the filament-daisy-ui-themes plugin in a Filament panel?
- Install it with Composer using composer require osamanagi/filament-daisy-ui-themes, then register FilamentDaisyUiThemesPlugin in your panel provider through the standard $panel->plugin(...) chain, so it follows the normal Filament plugin path instead of a bespoke theming layer. Publish the package assets with the filament-daisy-ui-themes-assets tag so the CSS and JS land in your application. After that, select a daisyUI theme in the plugin configuration and your buttons, tables, forms, and navigation pick up matching colors.
- Which Filament and PHP versions does this DaisyUI theme package support?
- The README targets Filament v3 panels, while a technical review of the package describes it as mapping daisyUI onto Filament 4/5 with PHP 8.2 or newer, so treat the version matrix as something to confirm against your own composer.json before pinning. Composer dependency resolution enforces the declared constraints at install time, which is your first line of defence. Run a short spike on your exact Laravel, Filament, and PHP versions rather than trusting a badge alone.
- Do I need Tailwind CSS and daisyUI installed to use this package?
- In practice yes. The package maps daisyUI's CSS-variable theme system onto Filament's UI, so it assumes Tailwind and daisyUI are present or acceptable in your frontend build. If your admin panel is not on a Tailwind/daisyUI stack, the tokens have nothing to attach to and you would be adding a dependency for little visual gain. Check how your host Tailwind configuration interacts with the published CSS so you do not hit specificity conflicts.
- How do I publish the theme assets, and are they built or committed?
- Publish them with php artisan vendor:publish --tag="filament-daisy-ui-themes-assets". The operational question that matters is whether assets are generated at install time, generated at build time via the repo's npm run build:themes and npm run check:themes scripts, or committed to your application, so decide this explicitly before your first deploy. Either way, add a verification step to CI so generated CSS drift is caught before release, and re-publish after upgrades so stale cached assets do not mask changes.
- Can I customize the colors instead of using a built-in DaisyUI theme?
- Yes. The documented customization path is CSS variables, which lets you change palette values without wrestling with Tailwind overrides. You can start from a prebuilt theme with light and dark variants and adjust only the tokens you care about, or define your own set. Keep your overrides in your own stylesheet so package updates do not overwrite them.
- Is there a runtime theme switcher, and how does dark mode work?
- The package exposes a Nagi\FilamentDaisyUiThemes facade alongside the plugin, but it is not yet clear whether that facade is a stable runtime API for a switcher or incidental to plugin registration. Built-in themes ship with light and dark variants, so basic dark mode works without custom code. If you need per-user or per-panel theme switching, spike the facade early and confirm its stability contract before building UI on top of it.
- Is filament-daisy-ui-themes safe to use in production?
- The engineering hygiene is stronger than the adoption numbers suggest: Pest with Testbench, PHPStan/Larastan level 4, Pint, Rector, browser compatibility checks, and an aggregate Composer verify gate are all in place. The risk is maturity rather than code quality, with a single maintainer, near-zero dependents, thin star counts, and an anomalous future release date that should be verified before you pin a version. The MIT license removes legal friction but not operational continuity, so plan a time-boxed pilot on one non-critical panel with a documented rollback to Filament's native theming.
- How is this different from just customizing Filament's native theme?
- Filament's native theme customization through a custom CSS file and Tailwind config carries zero extra dependencies and usually wins if your requirement is simply changing one accent color. This package wins when your public product already speaks Tailwind and daisyUI, because theme tokens become one shared vocabulary instead of two design languages. For non-Tailwind frontends or older Filament versions, stick with the native approach.
- What happens when Filament 6 or a new daisyUI major is released?
- Expect tight coupling to Filament major versions and a specific daisyUI major, so a Filament 6 or daisyUI major release will likely need work from the maintainer before you can upgrade. Keep the version pinned, test upgrades on a non-critical panel first, and clear published and cached assets as part of the upgrade. Keep a documented path back to Filament's native theme customization so you can drop the dependency without a rewrite.
- How do I test theme switching and check the package quality before rollout?
- Run the package's own Pest suite with Testbench plus PHPStan/Larastan level 4, Pint, Rector, and the Composer verify gate locally to confirm it is healthy on your PHP version. Add your own smoke test that boots a panel with the plugin registered and asserts the theme assets resolve. Also verify behaviour under dark mode, RTL layouts, and your existing admin panel CSP rules, since those are the areas a package test suite is least likely to cover for you.