- Is saad-tazi/g-chart-bundle a Laravel package?
- No. It is a Symfony2 bundle, confirmed by the Bundle suffix, the SaadTazi vendor namespace, and the typical DependencyInjection and Resources/config/services.yml layout. It has no Laravel service provider, no facade, and no Blade integration, so it will not auto-discover in a Laravel application. Treat it as a snippet library to extract rather than a dependency to install.
- Can I install it with Composer in a Laravel 10 or 11 app?
- Most likely not. The package predates PSR-4 adoption in that ecosystem and has no Composer constraint compatible with a modern Laravel release, so a composer require will either fail resolution or pull in an incompatible Symfony major. The realistic path is to copy the helper classes into app/Support/Charts, add declare(strict_types=1), and wrap them behind a small service provider.
- What does this bundle actually contain?
- It is a thin set of helper and service classes that format query strings and options for three Google chart surfaces: the JavaScript Chart Tools library, the legacy Chart Image API for static PNG and GIF URLs, and Google Infographics. The reusable value is a few hundred lines of URL and DTO construction rather than an architectural component. There is no rendering engine of its own.
- Do the static chart image features still work?
- No. The Google Chart Image API was deprecated in 2012 and turned off in March 2015, and Google Infographics was deprecated on a similar timeline. Any code path that produces a static chart URL now points at dead endpoints and will fail silently or emit broken img tags. Two of the bundle's three advertised capabilities are therefore non-functional today.
- Is the interactive chart rendering still supported?
- The Chart Tools Visualization API path still renders, but it is legacy. Google now steers users toward Looker Studio and third-party libraries such as Chart.js, ApexCharts, and ECharts. If you need long-term support, plan to swap the renderer rather than build around this bundle.
- How do I integrate it into a Laravel application?
- Extract the URL and option-building logic into a framework-agnostic ChartBuilder class with no Symfony imports, register it as a singleton in a service provider, and expose a Blade component or directive for the view layer. Keep the class free of Google-specific assumptions so the renderer can be replaced later. Budget about a day, not a sprint.
- Is the package well maintained and safe to depend on?
- It has roughly 20 stars and zero dependents, which means no downstream users exercising it, no issue triage, and no security response process. The MIT license is permissive and the code is small enough to audit in an afternoon, which is its one genuinely favourable factor. Supply-chain risk is near zero precisely because you should not be installing it.
- Does it support modern PHP versions and syntax?
- It is written against PHP 5.x-era idioms, likely including array() syntax with no scalar type hints or return types. There is no evidence of ongoing compatibility work for PHP 8.x. If you vendor the classes, add strict types and update the signatures yourself.
- What are the alternatives for charts in a Laravel app?
- For interactive client-side charts, use Chart.js, ApexCharts, or ECharts, which are actively maintained and framework-agnostic. For static server-side images, use a headless renderer or a maintained charting library rather than a Google URL API. If a contract mandates Google Charts, confirm whether Looker Studio covers the requirement.
- How should I test charts after integrating or extracting this code?
- Verify empirically which of the three API paths still produce working output, and expect the Image Charts and Infographics paths to fail. Test the fallback rendering path for when Google's JavaScript fails to load due to CSP, ad blockers, or offline conditions. Also confirm who owns the extracted code and whether it is a maintained fork or a temporary bridge.