- How do I install gigerit/larapex-charts in a Laravel application?
- Install it with Composer using composer require gigerit/larapex-charts, then follow the package documentation to publish any config or assets needed for your setup. Build chart objects in a controller or Livewire component and render them in Blade. Run your application tests and validate one representative chart in staging before rolling the package out across dashboards.
- Which Laravel and PHP versions does gigerit/larapex-charts support?
- Check the package composer.json for the exact PHP and Laravel version constraints, because those are the source of truth for compatibility. The package follows standard Laravel package conventions, and v10.1.0 introduces no runtime API changes or breaking changes from v10.0.0. Validate the constraints against your application before pinning the package.
- Do I need to write JavaScript to render charts with gigerit/larapex-charts?
- No, you define the chart type, series, labels, and options with the fluent PHP API and render the container and script in Blade. ApexCharts JavaScript assets are still required client-side to draw the chart. The package removes hand-written JavaScript configuration, not the browser-side charting runtime.
- Are ApexCharts assets loaded from a CDN or published locally with this Laravel package?
- The package follows Laravel conventions with publishable assets and config, so confirm the asset delivery approach in the documentation for your version. Many teams publish assets locally to satisfy CSP and version-pinning requirements rather than relying on a CDN. Check the bundled ApexCharts version and how it fits your asset pipeline before production.
- Can I use gigerit/larapex-charts with Livewire or Inertia?
- It fits Blade and Livewire dashboards naturally because chart configuration is built server-side in PHP. For Inertia or React and Vue frontends, you can still use it to produce chart options, but compare that with using ApexCharts directly to avoid duplicate chart abstractions. Test re-renders and data updates in your chosen frontend integration.
- What chart types are supported by gigerit/larapex-charts?
- The package supports common ApexCharts types such as line, bar, and pie, and exposes chart options through the fluent API. For less common ApexCharts types or advanced features, map the required options and verify rendering against the ApexCharts version you ship. Keep a smoke test for each chart type your application relies on.
- How do I customize colors, labels, axes, and tooltips in Laravel charts?
- Colors, labels, axes, tooltips, and other ApexCharts options are configured through the PHP chart object. Pass options as arrays and keep them centralized so package upgrades are easier to regression-test. Malformed option arrays are a common failure mode, so validate representative charts in staging.
- What are the practical limits for large datasets with gigerit/larapex-charts?
- Rendering happens client-side in ApexCharts, so very large datasets can hit browser memory and responsiveness limits. Aggregate, paginate, or downsample data before sending it to the chart, and watch the serialized payload size. Server-side cost is mainly data preparation and JSON serialization.
- How should I handle CSP and accessibility with gigerit/larapex-charts?
- ApexCharts remains a JavaScript dependency, so CSP headers must allow the chart assets and scripts you actually use. Publishing assets locally helps with version pinning and strict CSP policies. For accessibility, review ApexCharts behavior and test keyboard and screen-reader use cases rather than assuming the package handles conformance.
- Is gigerit/larapex-charts actively maintained, and is v10.1.0 safe to upgrade to?
- v10.1.0 has no runtime API changes or breaking changes compared with v10.0.0, so it is a low-risk Composer update for most Laravel applications. The release focuses on engineering quality such as Rector, PHPStan levels 1 through 8, CI, and documentation. The package is community-supported without a commercial SLA, so pin the version and run regression tests around chart rendering and asset delivery.