- Is laurentmuller/highcharts-bundle a Laravel package?
- No. It is a Symfony Bundle built around Symfony's bundle, dependency-injection, and controller-resolver model, so there is no Laravel service provider, facade, config publish tag, or Blade component. The underlying PHP object model that composes Highcharts option arrays is framework-agnostic and can be consumed from Laravel, but you must wire it up yourself.
- How do I install and configure laurentmuller/highcharts-bundle in a Laravel application?
- Install it with Composer, but do not expect Laravel package auto-discovery to register anything useful. The realistic path is to bind the option-builder classes you need in your own service provider or resolve them directly from Laravel's container. Before adopting, check that its declared Symfony and PHP constraints intersect cleanly with your Laravel and PHP baselines.
- Can I render Highcharts charts in Blade views with this package?
- Not out of the box, because the bundle ships no Blade component or view helper. The workable pattern is to assemble chart option arrays server-side, JSON-encode them into a div via a Blade partial, and let Highcharts initialize in JavaScript. You will write that partial and the client-side bootstrap yourself.
- Which Laravel and PHP versions does laurentmuller/highcharts-bundle support?
- That is not documented in the overview and depends entirely on the Symfony and PHP constraints declared in its composer.json. A bundle that lags Symfony's major-version cadence can drag PHP version constraints through transitive dependencies and pin you out of a Laravel upgrade path. Verify the constraint intersection against your baseline before committing.
- Do I need a commercial Highcharts license to use this bundle?
- The package itself is MIT licensed, but Highcharts is not, and commercial use of the Highcharts runtime requires a paid license. You also need to confirm whether the bundle bundles the runtime or references a CDN, since that changes your distribution obligations. Treat licensing as a budgeting and legal item, not a technical footnote.
- What are the alternatives to using this package for charting in Laravel?
- The strongest alternative is shipping Highcharts via Vite or npm and writing a small in-house PHP option builder plus a single Blade component that hydrates a div with JSON-encoded options. Given zero stars, zero dependents, and a composite score of 0.03, the in-house route carries materially less supply-chain and maintenance risk for equivalent delivered value. You can still seed your builder from this package's classes if the spike shows they are framework-free.
- Does laurentmuller/highcharts-bundle depend on Twig or other Symfony helpers?
- That is unverified and is the first thing a spike should establish. If the rendering path assumes Twig, Symfony's asset or CSRF helpers, or the configuration tree, you would be rewriting rather than rewiring for Laravel. Confirm which classes are truly framework-free before planning any adoption.
- How do I test charts built with this package in a Laravel application?
- No Laravel-specific testing helpers ship with the bundle, so assert on the option arrays your builder produces using PHPUnit. For the rendering layer, add a JS-level smoke test that confirms the container hydrates with valid JSON and that Highcharts initializes. Freeze the upstream version so your assertions do not drift with upstream changes.
- Is laurentmuller/highcharts-bundle actively maintained?
- There is no community validation to point to: zero stars, zero dependents, and no observable issue-tracker pressure indicating production use. Commit cadence over the last 12 months and any release or versioning discipline you can pin against are unverified. Treat it as a port candidate rather than a drop-in dependency.
- What is the recommended integration approach if we adopt this bundle in Laravel?
- Adopt in three moves: first spike the package in isolation to confirm which classes are framework-free, then vendor only those classes behind a Laravel service provider under your own namespace with the upstream version frozen and the extraction point recorded, and finally replace any remaining upstream coupling with your own builder. The exit ramp is deliberately short, so if upstream goes dormant or a Highcharts major version lands you own the code you need and discard the rest.