- Can I use fungio/google-map-bundle in a Laravel application?
- No. fungio/google-map-bundle is a Symfony bundle: it ships a Bundle subclass and a DependencyInjection extension, and Laravel's package discovery has no mechanism to register either of those. In a Laravel app the bundle layer is dead weight, and only the underlying map-building classes could conceivably be reused, which means manual wiring through a service provider. Treat it as a Symfony-only package when you are evaluating it.
- What does fungio/google-map-bundle actually do?
- It is a Symfony bundle that adds Google Maps API v3 support to your templates. It provides configuration plus Twig helpers for rendering a map, its markers, and controls, so you avoid hand-writing repetitive JavaScript in every view. Its scope is rendering and configuration rather than geocoding, server-side clustering, or other map logic.
- Does it work with Laravel 10 or 11 and PHP 8.1+?
- Almost certainly not. The bundle targets Symfony 4, which reached end of life in November 2023, which implies PHP 7.x constraints that conflict with Laravel 10 and 11 on PHP 8.1 and above. Expect Composer dependency resolution errors on a modern runtime before you write a single line of application code. Check the exact composer.json constraints for PHP and Symfony before assuming an install is possible.
- How do I install and configure fungio/google-map-bundle?
- In Symfony you would require it with Composer, register the bundle in your kernel or bundles.php, supply your Google Maps API key through bundle configuration, and then use the Twig helpers in templates. In Laravel there is no supported install path: you would have to fork the repository and strip the Bundle, DependencyInjection, and Twig layers. That work is only worthwhile if a short spike shows the map-building core is framework-agnostic.
- Is fungio/google-map-bundle actively maintained?
- No. Adoption signals are effectively zero: around 2 GitHub stars, 0 dependents, a single maintainer, and no visible release cadence or security disclosure path. There is no downstream usage from which to infer API stability. For a production dependency that means you own all future maintenance yourself.
- Does the package have tests or CI?
- The repository shows no evidence of a test suite or a CI pipeline, and the low adoption means no third party has validated it either. That matters more than usual here because the package wraps a third-party API whose behaviour and billing rules change over time. If you vendor the code, plan to add your own tests and run a static analysis pass such as PHPStan before relying on it.
- What is the best Laravel alternative for rendering a Google Map with markers?
- For most Laravel projects the need is simply rendering a map with markers, which is a small Blade component: a container div, the Google Maps JavaScript API loaded with a config-driven key, and a PHP DTO describing markers and polygons. That route takes one to two weeks to reach production quality but inherits no risk. If you prefer a package, choose a maintained Laravel-specific wrapper with recent releases and tests rather than an abandoned Symfony bundle.
- Which Google Maps APIs does it use, and are the generated calls still supported and billable?
- The documentation does not clearly state whether it wraps an existing library or emits raw JavaScript itself, and it is unclear which Google APIs it targets. Google's Maps JavaScript API key requirements, billing enforcement, and quota policies have changed repeatedly, so a stale wrapper may emit deprecated or unpriced calls. Confirm the actual API surface before relying on anything it generates.
- How much effort is it to salvage or migrate away from this bundle?
- The technical assessment puts salvage at roughly three to five days for a Laravel service provider and Blade component wrapped around a stripped core, assuming the core turns out to be framework-agnostic. A clean replacement is one to two weeks to production quality with no inherited risk. Timebox a one-to-two day spike first so you can make a clear go or no-go decision.
- Are there GDPR, cookie, or CSP concerns with embedding Google Maps?
- Yes. Embedded Google Maps load third-party scripts and can set third-party cookies, which is directly relevant to GDPR and CCPA consent flows as well as your Content Security Policy headers. The bundle's MIT licence does not cover Google Maps terms of service, which are separate and stricter. Budget for a consent gate and CSP allowances whichever integration route you choose.