Filament Leaflet Map Laravel Package

Product Decisions This Supports

• Map-based admin UX in Filament panels: If your product surfaces geographic data (store locations, delivery zones, asset tracking, customer addresses, field service sites), this package lets you add an interactive Leaflet map directly into Filament forms and tables rather than building a custom Vue/Livewire map component from scratch.
• Build vs. buy (well, "build vs. adopt"): A Leaflet wrapper is a classic commodity integration. The build cost is not the JS library — it's the Filament field wiring, state hydration/dehydration, validation, and asset loading. A package like this collapses that to a composer install, freeing engineering time for differentiated work.
• Feature scoping for geo features: Use it to cheaply prototype whether map-centric admin workflows (pick a point, draw a boundary, view pins) are valuable to users before committing to a heavier GIS stack (Mapbox, Google Maps, PostGIS-backed tooling).
• Roadmap input on vendor/lock-in posture: Leaflet + OpenStreetMap tiles means no per-map-load billing and no proprietary SDK lock-in — relevant if you're cost-sensitive or have data-residency constraints that argue against Google/Mapbox.
• Use cases to validate against: single-point pickers (address → lat/lng), multi-marker display for records lists, and simple polygon/area selection. Confirm which of these the 0.1.0 API actually supports before promising them to stakeholders.

When to Consider This Package

• Adopt (pilot) when: you're already on Filament v3/v4, you need an admin-side map field, your requirements are modest (point selection, marker display), and you're comfortable pinning a 0.1.x dependency behind a feature flag.
• Adopt with caution when: you need it in a customer-facing surface (this is a Filament plugin — it targets admin panels), or you require guaranteed API stability across upgrades.
• Look elsewhere when: you need geocoding, routing, clustering at scale, offline tiles, or server-side spatial queries — those are separate concerns this package almost certainly does not cover. Also look elsewhere if you need a supported, SLA-backed dependency; a 0.1.0 release with a changelog consisting only of a commit link is a signal of pre-stability, not a knock on quality.
• Red flags to check before adoption: version constraints against your Filament major version, whether assets are published/vendored (CSP and offline-build implications), test coverage, and whether the maintainer is a single individual (bus factor).
• Note on evidence: this assessment is based on a 0.1.0 release with no descriptive release notes beyond the compare link. Treat the feature list above as the expected scope of a Filament Leaflet plugin, and verify against the README and source before committing.

How to Pitch It (Stakeholders)

To executives: This is a small, low-cost open-source add-on that gives our admin panel interactive maps without licensing fees or a new vendor contract. It's early-stage (0.1.0), so we'd pilot it on an internal screen first — low downside, and it avoids us paying for Google Maps or Mapbox map loads.

To engineering: A Filament field that wraps Leaflet and handles the Livewire state plumbing we'd otherwise write ourselves. It does not remove the need to think about tile hosting, geocoding, or spatial storage — those stay our problem. Recommend pinning the version, reviewing the source (~small surface area), and gating behind a config flag until it stabilizes. Assess bus factor and upgrade path against our Filament version before we depend on it in a critical workflow.

Ask: a timeboxed spike (1–2 days) to validate the field against one real form, plus a decision point on whether we own a fork if the upstream stalls.