Weave Code
Filament Enhanced Charts Laravel Package
happenv-com/filament-enhanced-charts
Enhance your Filament admin panels with flexible chart widgets for Laravel. happenv-com/filament-enhanced-charts adds customizable visualizations to build richer dashboards faster, with simple integration into existing resources and pages.
Apache ECharts integration for Filament
Frequently asked questions about Filament Enhanced Charts
- What is happenv-com/filament-enhanced-charts and what does it do?
- It is a Filament panel plugin that extends Filament's built-in ChartWidget with richer, more configurable chart visualizations for admin panels and dashboards. It adds presentation-layer options such as customizable datasets, labels, visual styling, and widget header enhancements. It is not a separate charting abstraction; it builds on existing Filament chart widgets rather than replacing them.
- How do I install and register Filament Enhanced Charts in my Laravel panel?
- Install it with composer require happenv-com/filament-enhanced-charts, then register the plugin in your Filament panel provider. The v1.2.0 release does not indicate any migrations, published config, or queue and worker requirements. Integration effort is scoped to dashboard widget classes and their Blade views, typically a handful of files.
- Which Filament versions, v3 or v4, and PHP or Laravel versions are supported?
- The package is a Filament plugin, so matching the Filament major version in your application is the single gating condition. The v1.2.0 release does not provide a compatibility matrix for Filament v3 versus v4, or for PHP and Laravel ranges. Check the composer.json constraints and README before installing, and verify in a staging branch.
- Does this package replace Filament's ChartWidget or work alongside it?
- It works alongside Filament's ChartWidget and extends it rather than replacing it. The v1.2.0 release adds additive view-layer capabilities: a heading icon and an after-header Blade slot. Existing chart widgets continue to render unchanged unless a developer explicitly opts in.
- How do I add a heading icon to a Filament chart widget?
- The heading icon is exposed as a widget configuration option on your chart widget class, so consult the README for the exact property or method name. It is opt-in per widget, meaning existing dashboards render unchanged if you do not use it. This keeps upgrade risk low because adoption is explicit rather than automatic.
- How do I use the after-header Blade slot on a chart widget?
- The after-header slot is a view-layer extension added in v1.2.0 and is consumed from the widget's Blade view. That keeps coupling to Filament's presentation layer rather than to domain or application code. Because the slot is new, confirm with the maintainer whether it is a stable public API or an escape hatch that may be reworked.
- What charting engine renders underneath, Chart.js, ApexCharts, or ECharts?
- The available repository context does not identify the underlying charting engine. The v1.2.0 release does not appear to change data-fetching behaviour, but asset publishing and JS bundle changes are not documented. Verify the engine, asset publishing, and any custom JS implications with the maintainer before relying on them.
- Is it safe to upgrade from v1.1.0 to v1.2.0 in production?
- The v1.1.0 to v1.2.0 change is additive by inspection, consisting of a feature plus chore and CI updates, so the upgrade is typically a version-constraint bump and composer update. Existing dashboards render unchanged unless you adopt the new heading icon or after-header slot. Still verify the Filament major version match and whether your app has customised the chart widget header view.
- How is the package tested, and is CI enforcing widget rendering tests?
- The release context does not document a snapshot, Dusk, or Pest test suite for widget rendering. CI does show positive maturity signals such as TruffleHog secret scanning, Dependabot groups, Copilot code review, and a Laravel Moat configuration for boundary enforcement. Those reduce risk but are not the same as rendering test coverage, so ask the maintainer what automated tests exist and whether CI enforces them.
- Is Filament Enhanced Charts actively maintained, and what are the alternatives?
- The project is small, early, and effectively single-maintainer, so treat it as a convenience dependency rather than load-bearing infrastructure. It fits teams that want cosmetic, compositional enhancement of Filament dashboard widgets without a parallel charting abstraction. A Filament major version bump is the most likely future breakage point, and teams needing a full charting alternative should evaluate other Filament chart plugins.
Weaver
How can I help you explore Laravel packages today?