- What is aabosham/filament-spark-pie and what does it do?
- aabosham/filament-spark-pie is a Laravel package that plugs into Filament to render compact Sparkline pie charts in tables, dashboards, and infolist builders. It is meant for quick visual summaries of data distributions rather than full-featured charting. The package is only relevant if your application already uses Filament, specifically Filament v3 for the 2.x line. Documentation is sparse, so verify behavior against the repository README and source before adopting it.
- How do I install aabosham/filament-spark-pie in a Laravel Filament v3 app?
- Install it with Composer using a v2 constraint, for example composer require aabosham/filament-spark-pie:^2.0, then register the plugin in your Filament panel provider as described in the package README. Because release notes are sparse, confirm the exact provider class and any asset publishing commands from the source. Test the install in a staging branch before rolling it out. If you are upgrading from v0.0.4, treat it as a breaking change and review the changelog.
- Does filament-spark-pie support Filament v3 and Laravel 10?
- The 2.0.0 release explicitly adds Filament v3 support, so that is the line to use with a Filament v3 admin panel. Filament v3 generally implies Laravel 10 or 11 and PHP 8.1 or 8.2, but you should confirm the package composer.json constraints against your host app. The major jump from 0.0.4 to 2.0.0 suggests the older release targeted a different Filament API. Do not assume Filament v2 support remains in 2.x.
- Can I use filament-spark-pie in a non-Filament Laravel application?
- No. filament-spark-pie is a Filament plugin and widget, so it only makes sense inside a Laravel application that already runs Filament v3. Non-Filament Laravel apps and non-Laravel PHP projects should use a different charting approach. If you are still on Filament v2, defer adoption until you plan a Filament v3 upgrade.
- How do I add a spark pie chart to a Filament infolist or table?
- The 2.0.0 release notes mention targeting Filament's infolist builder, but the exact schema component or configuration is not documented in the provided notes. Start by reading the package README and source to see how the component is registered and how data is passed in. Add it to a test resource's infolist in staging and validate rendering, data binding, and responsive behavior before production. The same caution applies to table and dashboard usage.
- What are the breaking changes from v0.0.4 to v2.0.0?
- There is no documented migration guide, and the version jump from 0.0.4 to 2.0.0 strongly implies breaking API or configuration changes. Treat any upgrade as a breaking change: review the full changelog, test in a branch, and expect to reverse-engineer configuration differences. Avoid upgrading the package and Filament simultaneously in production. Pin to a specific minor version and monitor releases.
- Is filament-spark-pie actively maintained and safe for production?
- The package appears to be a small, likely single-maintainer project with sparse release notes and community-only support via GitHub issues. That creates abandonment and lag risk behind Filament major releases, so production use should be gated by staging smoke tests and a pinned version. There is no commercial SLA. Capture internal knowledge after integration and be prepared to fork or replace the package if needed.
- Does filament-spark-pie require publishing assets or a JavaScript dependency?
- The provided notes do not confirm asset publishing requirements or the underlying JavaScript dependency, though a Sparkline-based chart is likely rendered client-side. Check the README and source for publish commands, compiled assets, and caching behavior. Missing or stale assets can cause silent chart rendering failures. Validate in staging with your frontend asset pipeline before production.
- Can I customize colors, labels, sizes, and tooltips in filament-spark-pie?
- The package blurb says colors, labels, sizes, and tooltips are configurable, but the exact API and option names are not documented in the provided context. Inspect the README and source for the component's configuration methods. Test each option in a staging resource to confirm behavior. Do not assume parity with other Filament chart packages.
- What alternatives exist if filament-spark-pie is abandoned or incompatible?
- If the package is abandoned or incompatible, consider Filament's built-in chart widgets, a custom Blade view with a maintained JavaScript chart library, or another actively maintained Filament chart plugin. The right choice depends on whether you need compact sparkline-style pies or full interactive charts. Budget time for a fork if you rely on the existing behavior. Keep the replacement scoped to admin infolist and dashboard pages.