- Can I install rcousens/amcharts-bundle in a Laravel application?
- Not as a working integration. It is a Symfony2 bundle that registers through AppKernel and depends on Symfony DI and Twig helpers, so Composer will typically fail dependency resolution against modern Laravel. Even if forced, none of the Symfony wiring runs in a Laravel app, so treat it as reference code for a chart config builder rather than a drop-in dependency.
- Does rcousens/amcharts-bundle support Laravel 10 or 11?
- No. The package predates modern Laravel and targets Symfony 2.x and PHP 5.x, with a last release in July 2014. There is no service provider, facade, Blade directive, or Laravel-compatible config publishing.
- What PHP versions does this AmCharts bundle require?
- It was written for PHP 5.x-era Symfony 2.x and uses idioms that are removed or deprecated in PHP 8.x. Expect fatal errors such as removed functions and old container APIs. A fork and patching are required before it runs on PHP 8.1 or newer.
- How do I use amCharts with Laravel Blade instead of Symfony Twig?
- Extract the bundle's chart configuration logic into plain PHP, then wrap it in a Laravel service provider and a Blade component or directive. The component should emit a container div, a safely escaped JSON payload, and an init script. Replace the 2014-era bundled amCharts JS with a currently maintained version.
- Is rcousens/amcharts-bundle still maintained?
- No. The last release was July 2014 and the repository shows no meaningful community activity, with zero dependents. Symfony 2.x reached end of life in November 2018, so there are no security or compatibility updates.
- What Laravel alternatives exist for amCharts or charting?
- Consider Lavacharts, consoletvs/charts, or a thin Laravel wrapper around a modern JavaScript chart library. You can also build a small config-to-JSON service and use amCharts v5 directly in Blade. Each option avoids carrying abandoned Symfony 2 code into a new stack.
- What is the migration path from this Symfony bundle to Laravel?
- Fork or vendor the repo, pin the commit, and preserve the MIT license notice. Isolate the chart config builder into framework-agnostic PHP, delete the Symfony DI, bundle, and Twig classes, then add a Laravel service provider, config file, facade, and Blade component. Finally, replace the old amCharts assets with a maintained chart library.
- Which amCharts JavaScript version is bundled with this package?
- The bundle is from the Symfony 2 era and references an AmCharts 2 or 3-era JavaScript build, not modern v4 or v5. It is unclear from the package whether the JS is vendored or loaded from a CDN. Verify the asset source and licensing before reusing it, and expect dead CDN links in a 2014 bundle.
- Can I use rcousens/amcharts-bundle in production?
- No, not safely in a Laravel production application. It is abandoned, untested against modern PHP, and has no meaningful test suite or dependent community. Running it risks fatal errors, unpatched assets, and XSS issues around JSON payload escaping.
- Are there tests or examples for the expected chart config schema?
- The bundle has no test suite of consequence and only limited examples, so you cannot rely on it to document the config schema. When forking, add your own fixtures and characterization tests around the extracted builder. Static analysis with PHPStan at a low level will surface removed functions and dynamic property usage early.