- How do I install arukompas/livewire-charts in a Laravel Livewire app?
- Install it with Composer using composer require arukompas/livewire-charts, then publish the package assets with the vendor:publish command so the charting JavaScript is available to your front end. After that you render charts by using the package's Livewire components directly in your Blade views. There are no database migrations, queues, or extra service providers to configure beyond the package itself.
- Which chart types does livewire-charts support?
- The package ships components for line, area, bar, pie, donut, radial, and polar charts. Each one is a Livewire component you configure from PHP with your own data and options. Because it wraps the ApexCharts engine, most ApexCharts display options are available to pass through.
- Which Laravel and Livewire versions does arukompas/livewire-charts support?
- Version 3.3.0 adds declared Laravel 13 support, and the 3.x line targets modern Livewire releases. The authoritative answer is the version constraint declared in the package's composer.json, so check that it admits both your Laravel framework version and your Livewire major before upgrading. If you need to run Laravel 12 in parallel, confirm the constraint still allows it rather than assuming from the release notes.
- Do I need JavaScript or a front-end build pipeline to use livewire-charts?
- No. The package provides publishable assets and Blade-friendly components, so you do not need to stand up a separate JS build pipeline or hand-wire chart initialisation. You still depend on the underlying ApexCharts JavaScript at runtime, so bundle size, CSP behaviour, and rendering performance are governed by that library rather than by this package.
- How do charts update when my Livewire component state changes?
- You define chart data and options as Livewire properties, and the chart components re-render reactively when that state changes. There is no manual JavaScript wiring or custom event handling required on your side. This makes the package a good fit for dashboards and filters where datasets and labels change in response to user input.
- How do I customise chart options and styling with livewire-charts?
- You pass ApexCharts options as arrays from your Livewire component, alongside the dataset and labels, so colours, axes, tooltips, and legends are all configured in PHP. Styling ultimately maps to the underlying charting engine, so its documentation is the reference for individual option names. Changes to those PHP properties propagate to the rendered chart reactively.
- Is upgrading livewire-charts from 3.2.x to 3.3.0 a breaking change?
- No, 3.3.0 is a minor release with no stated breaking changes, so the expected path is to bump the constraint to ^3.3, run composer update arukompas/livewire-charts, re-publish assets if the underlying charting engine version moved, and smoke-test each chart component. There is no data or schema migration involved. Moving from v2 or earlier is a different story: treat it as a major migration because component APIs and asset directives changed across the v3 boundary.
- Can I use livewire-charts with Inertia, Vue, React, or an API-only Laravel app?
- It is not a good fit for those surfaces. The package is a presentation-layer wrapper for Livewire-rendered Blade views, so Inertia, Vue, or React front ends are cleaner with a native charting library as a direct dependency. It also does not render server-side chart images, so it cannot cover export or PDF-report use cases on its own.
- Is livewire-charts safe to depend on long term given it is maintained by a single author?
- It is a single-author package, so bus-factor risk is real and worth weighing for anything long-lived. The maintainer shipping the Laravel 13 compatibility commit himself is a reassuring signal of intent, but it does not remove key-person exposure. Mitigate by pinning versions, checking whether a support window or deprecation path is documented for the next major, and being ready to swap in a direct ApexCharts integration if maintenance stalls.
- What production concerns should I check before shipping livewire-charts, such as assets, CSP, caching, empty datasets, and timezones?
- Confirm assets publish with a version hash so you can use long-lived caching without stale chart code, and verify CSP compliance, since scripts come from the underlying JavaScript library and may not be eval-free. Test the Livewire re-render lifecycle to ensure charts are destroyed and recreated correctly, and check behaviour with empty datasets and timezone-localised axes. Finally, look at the CI matrix: a widened Composer constraint for Laravel 13 is not the same as tests actually executing against Laravel 13.