- What is eightynine/filament-advanced-widgets used for?
- It is an additive UI package for Filament admin panels that provides advanced widget components for dashboards, such as charts, stats, tables, and custom views. It is meant to enrich an existing Laravel and Filament application, not to define domain architecture. If your app is not built on Filament, it is a poor fit.
- How do I install filament-advanced-widgets in a Laravel Filament app?
- Install it with Composer and register the widgets in a Filament panel or provider, following the package README for any required asset or config publishing. Because exact setup steps depend on the package version, confirm the commands against its documentation and your Filament major version. Start in a non-production panel or feature-flagged dashboard before rolling it out.
- Which Filament versions does filament-advanced-widgets support?
- The supported Filament versions are defined by the package's Composer constraints, so inspect its composer.json and release notes before adoption. The package is a Filament UI-layer addition, so matching its Filament major version to your panel is the key compatibility check. Do not assume support for older or newer Filament releases without verifying.
- Is filament-advanced-widgets compatible with my Laravel, PHP, and Livewire versions?
- Check the package's Composer constraints against your application's Laravel, PHP, Livewire, and Filament versions before installing. A short technical spike is wise because version mismatches are the primary integration risk. Validate the dashboard in a production-like build, not only in local development.
- What widget types does the package provide for Filament dashboards?
- The package is positioned around richer Filament dashboard widgets, including charts, stats, tables, and custom views. Use these as optional dashboard enhancements where native Filament widgets do not cover the interaction or presentation you need. Confirm the exact component list in the README for your pinned version.
- Can I use filament-advanced-widgets in production?
- It can be used in production, but the package has limited adoption signals, including a small star count and zero dependents, so treat it as a candidate component rather than a strategic dependency. Run a one-widget proof of concept with realistic data volume and permissions first. Integrate behind a feature flag with a native-widget fallback and pin the version.
- Do I need to publish assets or configure Tailwind for filament-advanced-widgets?
- Plan to publish and review any assets or configuration the package documents, and verify Tailwind and asset compilation in CI. Asset pipeline conflicts are a known risk when adding dashboard UI packages to Filament. Confirm whether package views can be overridden so vendor markup stays isolated.
- How should I authorize and scope data used by advanced Filament widgets?
- Widget data queries should be authorized and scoped by your application, not left to the UI component. Define the data-source contracts, apply permission checks, and limit queries to the records the current admin user may see. Review query performance and add caching or aggregate tables if widgets poll frequently.
- Does filament-advanced-widgets have tests and CI?
- Check the repository for tests, CI configuration, open issues, and documented upgrade paths before committing. Expect your team to own compatibility testing for each Filament and Laravel upgrade, and budget for occasional patches or a maintained fork under the MIT license. Pin versions and avoid unreviewed automatic upgrades.
- Should I use filament-advanced-widgets or native Filament widgets?
- If you only need standard stats or charts, prefer native Filament widgets first because they carry less compatibility and maintenance risk. Use filament-advanced-widgets when its extra widget components clearly reduce build effort and pass your technical spike. Keep a native-widget fallback for dashboard continuity.