- What is imumz/leaflet-map used for?
- It is a Laravel package for embedding interactive Leaflet maps, described as a custom Laravel Nova map field built with Vue2Leaflet. The overview also mentions a fluent API for maps, markers, popups, GeoJSON layers, controls, publishable config, and reusable view components. In practice it is an admin-plane coordinate picker, not a server-side geocoding or spatial-querying system.
- Does imumz/leaflet-map work with Laravel Nova 4 or Nova 5?
- There is no evidence that it supports Nova 4 or 5. The last release was January 2021, which predates Nova 4's Vue 2 to Vue 3 migration and the Laravel 9, 10, and 11 era. Assume breakage until you validate composer resolution and the Vue component in a licensed Nova environment, and expect to fork it to loosen version constraints.
- Which Laravel and PHP versions does imumz/leaflet-map support?
- The provided context does not list exact Laravel or PHP constraints. Because the last release is from January 2021, its composer.json likely targets older illuminate/* and laravel/nova ranges. Inspect and test those constraints against your target stack before adoption; you may need to loosen them in a fork.
- How do I install imumz/leaflet-map with Composer?
- Install it with Composer using the imumz/leaflet-map package name, then rely on Laravel package auto-discovery or register the service provider if needed. For Nova use, publish Nova assets and register the field class in your Nova resource. Because the package is stale, expect dependency conflicts and validate installation in a throwaway branch first.
- Can I use imumz/leaflet-map in Blade views instead of Nova?
- The package overview describes a Laravel package for Blade views with a fluent API, but the technical assessment identifies it as a Nova field that wraps Leaflet in a Vue component. Treat that as a discrepancy to verify in the README and source before choosing it. For public-facing Blade maps, a maintained Leaflet integration or a small custom wrapper is likely safer.
- How does imumz/leaflet-map store latitude and longitude values?
- The package does not prescribe a persistence model; the host application decides. Common choices are two numeric latitude and longitude columns or a JSON attribute. You must handle nulls, validation, and coordinate precision yourself, because the package is a picker and does not provide spatial queries or projection handling.
- Which map tile provider does imumz/leaflet-map use, and how should I handle API keys?
- The context flags an unpinned third-party tile provider such as OSM, Google, or Mapbox but does not state which one is hard-coded. Check the source and config before use. Prefer a server-side configurable API key, review the provider's terms, rate limits, and privacy exposure, and never expose secret keys client-side.
- Is imumz/leaflet-map maintained and production-ready?
- The risk signals are high: 8 stars, 0 dependents, a single maintainer, no release since January 2021, and no evidence of CI or a test suite. It also carries a stale Leaflet version, an older compiled asset pipeline, and possible Nova major breakage. Treat it as a reference or fork with pinned dependencies, rebuilt assets, and smoke tests rather than a drop-in production dependency.
- Does imumz/leaflet-map support read-only fields, index views, and detail views?
- That is not confirmed in the provided context. The package assumes the standard Nova field contract, so behavior on create, update, detail, index, disabled, and read-only states must be validated. Budget a compatibility spike in a licensed Nova environment before relying on those states.
- Should I adopt imumz/leaflet-map or build my own Leaflet map field?
- The assessment recommends treating the package as a starting reference, not a dependency. Because the surface area is small, a one- to two-day in-house Leaflet field may be cheaper and safer than sustaining a fork. If you adopt it, fork the source, pin a commit, loosen version constraints, rebuild assets for the current Nova and Vue toolchain, add CI, and smoke-test value round-tripping.