Weave Code
Maps Bundle Laravel Package
nucleos/maps-bundle
Symfony bundle for adding interactive maps to your application. Configure map providers, render maps in Twig, and place markers and locations, keeping map setup centralized so pages can display geographic data with minimal effort and configuration.
nucleos/maps-bundle brings interactive maps to Symfony applications with minimal setup. It offers a service-oriented API and Twig helpers for embedding maps, defining markers, and feeding map data from your controllers and entities, while provider-specific details stay behind a configurable abstraction so templates remain clean.
- Twig helpers for rendering maps and markers
- Configurable map providers and tile layers
- Service-based PHP API for building map data
- Sensible bundle defaults with full Symfony DI configuration
- Straightforward integration with existing routing and Doctrine entities
Frequently asked questions about Maps Bundle
- Is nucleos/maps-bundle a Laravel package?
- No. nucleos/maps-bundle is a Symfony bundle for rendering interactive maps with configurable providers, marker support, and Twig helpers. It relies on Symfony bundle registration, the Symfony DI container, and Twig rather than Laravel's package discovery, service providers, and Blade. That architectural difference is the main reason it is not a drop-in dependency for a Laravel application.
- Can I use nucleos/maps-bundle directly in a Laravel application?
- Not without running a Symfony kernel or bootstrapping Symfony components alongside Laravel, which is disproportionate for a presentation-layer map widget. Laravel has no bundle registration mechanism, no Twig view layer by default, and no Symfony DI container to load the bundle's service definitions. The recommended path is to treat the bundle as a reference implementation and rebuild the map rendering as a first-party Laravel package with a Blade component, config file, service provider, and published JS assets.
- How do I install nucleos/maps-bundle?
- In a Symfony application, install it with Composer via composer require nucleos/maps-bundle, register the bundle in config/bundles.php, and configure the provider and rendering options in your Symfony configuration. It is a standard Symfony bundle install, not a Laravel package install. For Laravel, you would instead create or adopt a Laravel-native map package rather than installing this bundle.
- Which map providers does nucleos/maps-bundle support?
- The bundle advertises configurable map providers, so provider choice is intended to be set through configuration rather than hard-wired. The documentation is thin, so verify the actual supported providers, such as Leaflet with OpenStreetMap, Google Maps, or Mapbox, against the bundle's configuration and source before committing to it. If your requirement is a specific provider or rendering approach, confirm support early because swapping providers may require template or asset changes.
- Does nucleos/maps-bundle support markers and custom marker views?
- Yes, marker support and Twig helpers are part of the bundle's stated scope, covering simple location maps through richer marker-based views. Because rendering is driven by Twig templates and Symfony asset conventions, deep customization such as custom marker markup, clustering, or provider-specific behavior may require overriding templates or forking the bundle. Plan for that coupling if your map UI needs to diverge from the default output.
- Does nucleos/maps-bundle handle marker clustering or large marker volumes?
- The bundle appears focused on simple map rendering and marker display, and there is no clear indication that clustering, server-side geocoding, or large-volume marker optimization is built in. Before relying on it for dense datasets, review the source and configuration to confirm what is actually supported. If you need clustering or geocoding, expect to add that logic yourself or choose a different rendering approach.
- What Symfony versions does nucleos/maps-bundle support, and does it support Laravel versions?
- Version support is defined by the bundle's composer.json constraints, so check those against your Symfony version before adopting it. It does not declare Laravel version support because it is not a Laravel package and has no Laravel service provider or Blade integration. For a Laravel application, Laravel version compatibility is a question for whatever Laravel-native map package or first-party component you build instead.
- How do I test map rendering with nucleos/maps-bundle?
- In a Symfony application, test the rendered template output and the map configuration passed to the JavaScript widget using functional tests around the Twig helpers. In a Laravel application, you would instead test your own Blade component and the config or marker data it receives. Map rendering is presentation-only, so failures degrade a UI element rather than a transaction path, which keeps the testing surface small.
- Is nucleos/maps-bundle actively maintained and safe for production?
- Technical risk is low because the bundle only renders maps and introduces no migrations, authentication surface, or queue semantics. Adoption risk is higher: it has few stars and dependents, comes from a single vendor, and the listed 2026-05-01 release date should be verified against Packagist and the repository's tag history before treating it as actively maintained. The MIT license means you can fork and own it if needed, but you would be among the first external consumers.
- What are good alternatives to nucleos/maps-bundle for Laravel?
- For a Laravel stack, the practical alternative is to build a first-party package that wraps Leaflet, Mapbox, or Google Maps behind a Blade component, a config/maps.php file, a service provider, and published JS assets. That approach typically takes a few days for a simple map widget and gives you full control over providers, markers, and clustering. You can still use nucleos/maps-bundle as a design reference for marker data shapes, template structure, and asset wiring without taking on the Symfony coupling.
Weaver
How can I help you explore Laravel packages today?