Weave Code
Inline Chart Laravel Package
lara-zeus/inline-chart
Lara Zeus Inline Chart renders compact charts inline in Laravel and Filament interfaces—ideal for sparklines, trends, and at-a-glance metrics inside tables or text. Lightweight, simple to configure, and Blade-friendly, it keeps key numbers visible without bulky dashboards.
lara-zeus/inline-chart is a lightweight Filament plugin that renders inline charts directly inside your admin panel. Add sparklines, line charts, or bar charts to forms and tables without extra JavaScript or complex chart configuration.
- Fluent API for quick chart setup
- Multiple chart types (line, bar, sparkline)
- Responsive and theme-aware styling
- Customizable colors, labels, and datasets
- Seamless Filament integration
Frequently asked questions about Inline Chart
- How do I install lara-zeus/inline-chart in a Laravel Filament panel?
- Require it with composer require lara-zeus/inline-chart, then import the column class in the Filament resource, table, or widget where you want the chart. There is no migration, config file, or schema to publish because the package stores nothing. Check the PHP, Laravel, and Filament version floors in its composer.json rather than relying on the README. Pin by Filament major version rather than latest.
- Which Filament versions does lara-zeus/inline-chart support?
- The package is versioned by Filament major: Filament 3 and 4 map to ^2.0.4, while Filament 5 maps to ^3.0.0. Release 3.0.0's changelog is a single line stating Filament 5 support, so read the 2.0.4 to 3.0.0 diff before upgrading. Confirm that methods such as chartType, color, height, and data still exist in the installed src/, and treat the major bump as breaking until you have verified it.
- How do I render a sparkline inside a Filament table column?
- Add a column using the package's inline chart column class and chain the fluent options you need. It renders inside the table cell, so the chart sits next to the underlying value instead of on a separate dashboard page. Keep the series short and the number of chart columns sensible, since each cell is a client-side render.
- How do I pass data to the inline chart column?
- The data option accepts a plain array, a model attribute name, or a closure. Prefer a precomputed projection over a closure that queries per row: fn ($record) => Order::where(...)->pluck('total') turns a 25-row table into 25 extra queries per page load. If you must use a closure, eager load or pre-aggregate the series in the query that builds the table.
- Can I change the chart type, color, and height?
- Yes, the fluent API exposes chartType, color, and height alongside data, and the package ships line, bar, and sparkline chart types. Styling is responsive and theme-aware, so charts follow your panel's light and dark modes. Verify the exact method names against src/ in the version you install, especially after a major release.
- Does the inline chart column work with Filament table sorting, filtering, and exports?
- Sorting and filtering do not apply, because the column is a rendered visual rather than a database-backed value. Exports such as CSV or XLSX will emit the raw array or nothing unless you explicitly handle the column in your export definition. Test the export output before shipping a report that includes these tables.
- Is Chart.js bundled with lara-zeus/inline-chart or loaded from a CDN?
- Asset provenance is not documented, so verify it yourself in the installed package before deploying. If Chart.js is pulled from a CDN, that is both a supply-chain dependency and a CSP finding, and the charts will not render at all in an air-gapped or strict-CSP admin panel. Also confirm as part of your upgrade check that 3.x still ships and publishes a JS asset.
- What happens with an empty or single-point dataset in an inline chart?
- This behavior is undocumented and is the most common silent failure mode, so render a 0-point and a 1-point series in a staging panel before you rely on the column. A blank cell may mean bad data rather than a broken chart. Remember that one JS exception can degrade the whole table, so test failure cases deliberately.
- Does lara-zeus/inline-chart cause performance problems on large tables?
- The package adds no server-side rendering cost beyond the query you supply, so the risk is entirely in how you feed it data. Watch for per-row closures that fire one query per row, and measure the client-side render cost at your real page size and series length. A single JS exception in a cell can blank the table, which reads as a table bug rather than a chart bug.
- Is lara-zeus/inline-chart safe to adopt in production, or should I use something else?
- Adoption risk is moderate: single maintainer, roughly 23 stars, no dependents, MIT licensed, and you will be an early verifier of the Filament 5 path. The exit cost is low, about a couple of days of hand-rolled Chart.js in a column, so treat it as a standing risk-register entry rather than a blocker. Do not use it for exploration work such as drill-down, cross-filtering, axes, tooltips, or exports, and never for customer-facing or contractual reporting. For full dashboards, reach for a dedicated charting library instead.
Weaver
How can I help you explore Laravel packages today?