- How do I install LavaCharts in a Laravel application?
- Install the Composer package khill/lavacharts and let Laravel auto-discovery register the service provider and facade where supported on the 3.x line. If auto-discovery is not available, register the provider and alias manually in your Laravel configuration. The 3.1.14 release fixes a Composer 2 blocker related to the RenderableTrait issue, so use Composer 2 and verify the branch you install. Charts still load Google Charts from gstatic.com at runtime, so no JavaScript build step is required but browser access is.
- Does LavaCharts support Laravel 10 or Laravel 11?
- There is no stated support matrix for PHP 8.x or Laravel 9, 10, or 11 in the release notes, so treat those versions as untested until you verify install and runtime yourself. The package integrates through a Laravel service provider and facade, and the 3.x line supports auto-discovery, but that does not guarantee framework compatibility. The 3.1.14 patch only addresses a Composer 2 and RenderableTrait packaging issue, not Laravel version support.
- What is the difference between LavaCharts 3.x and 4.x, and which should I use?
- The published release referenced is 3.1.14, while earlier guidance may have been scoped to a 4.x line, and requirements, facade registration, auto-discovery, and PHP constraints can differ between lines. Confirm the intended supported branch before committing and verify that the RenderableTrait Composer 2 fix exists on the branch you install. Do not assume compatibility or fixes from one branch carry over to the other.
- Can LavaCharts render charts server-side for PDFs or emails?
- No. LavaCharts is a thin PHP-to-JavaScript translation layer: PHP builds the chart configuration, serializes it into inline JavaScript, and a div loads Google Charts loader.js in the browser. Rendering is entirely client-side and the server never rasterizes an image. For PDF, email, or scheduled report images you need a separate server-side chart renderer.
- Is LavaCharts safe for production use?
- Production suitability depends on gates: confirm the license, because GitHub reports NOASSERTION and MIT must be legally verified before commercial use, choose and verify the supported branch, and test PHP and Laravel compatibility yourself. The project had a roughly five-year release gap before 3.1.14, a narrow packaging patch with a one-line changelog, and limited ecosystem coverage with 619 stars and 0 tracked dependents. Also review the Google CDN dependency and PHP-to-JavaScript serialization and escaping risks against your CSP and data policies.
- What chart types does LavaCharts support?
- LavaCharts provides fluent builders for Line, Bar, Column, Pie, Donut, Geo, Scatter, Combo, Area, and Table charts. It also supports DataTables with formatters, calculated columns, and event handling. Dashboards, controls, and material charts may be available, but validate them against your product requirements and chosen branch.
- How does LavaCharts handle data tables and formatting?
- You build DataTables in PHP with rows, columns, formatters, and calculated columns, then attach them to chart configurations. Events can be wired without writing JavaScript boilerplate. Because configuration is marshalled to JavaScript, test special characters, dates, nulls, and script-closing sequences in your Blade output.
- Does LavaCharts require an internet connection or Google CDN?
- Yes for rendering: the Blade output pairs a div with a script that loads https://gstatic.com/charts/loader.js and uses the google.visualization API. There is no offline or self-hosted rasterization path in the package. If your CSP, third-party policy, or regulated data-residency rules block gstatic.com, plan an alternative.
- How do I render a LavaCharts chart in a Blade view?
- Build the chart in a controller or service provider using the fluent PHP API, then echo the rendered output unescaped in Blade so the div and inline script are emitted. Dimensions, options, and responsiveness are configurable on the chart object. The package is stateless, so no persistence, queues, or workers are involved.
- Is LavaCharts actively maintained, and what are the alternatives?
- Maintenance signal is weak but not dead: the prior release was 2020-11-23, and 3.1.14 is a post-2020 packaging fix with a one-line changelog and no visible CI or test cadence. Treat it as a pulse, not a cadence, and decide who owns a fork if upstream remains largely dormant. Alternatives include other Laravel chart wrappers or direct Google Charts JavaScript, but compare server-side rendering needs, CSP and CDN constraints, and license terms before switching.