- How do I install bagusindrayana/laravel-map in a Laravel application?
- Install it with Composer, then publish the package config and assets with vendor:publish. The package ships Blade views, JavaScript, and CSS for Leaflet, so confirm where published assets land in your app. Check the Composer constraints for PHP and Laravel before requiring it.
- Which Laravel and PHP versions does laravel-map support?
- The provided context does not list a complete PHP and Laravel support matrix. Verify the require constraints in the package composer.json against your runtime before adopting or upgrading. Because the v1.0.6 notes are terse, treat compatibility claims as provisional until checked in source.
- How do I render a map from a Laravel controller using this package?
- The package is designed to make and customize maps from controller code. Configure map settings and markers in the controller, then render through the package's Blade helpers and views. Keep map setup server-side and avoid duplicating Leaflet initialization in your own JavaScript.
- How do I add markers and customize map settings with laravel-map?
- Use the package helpers to define markers and map options, then render the map in Blade. Configuration may live in controller code or published config depending on how your app organizes settings. Re-publish assets after upgrades so the JavaScript and CSS match the package version.
- Does laravel-map work with Inertia, React, or Livewire front ends?
- The package assumes a Blade-centric Laravel rendering model. For Inertia, React, or Livewire-driven front ends, its value drops to asset bundling plus a config wrapper, so using Leaflet directly or a lighter wrapper may be preferable. Confirm fit before adopting it in an SPA-style application.
- What changed in laravel-map v1.0.6 and is the PSR-4 change breaking?
- The v1.0.6 notes list a PSR-4 name change, a Leaflet update, a JavaScript update, and a new fetch method. If the PSR-4 change renamed the package namespace rather than merely correcting autoload, it is a breaking change shipped in a patch release. Diff composer.json and the namespace directory layout, grep for the old namespace, facade alias, and config keys, and look for upgrade notes before merging.
- Which Leaflet version does laravel-map bundle?
- The release note says Leaflet was updated, but the exact bundled version is not stated in the provided context. Check the package source, published assets, or lockfile to confirm. Leaflet 1.x to 1.9 is generally safe, while a 2.x major would require plugin and API compatibility checks.
- How does the new fetch method in laravel-map work for loading map data?
- The fetch method addition suggests the package is moving from static map rendering toward client-side data loading. Its contract is not documented in the provided context: endpoint configuration, headers, CSRF handling, auth, abort or cancellation support, caching, and response mapping are all unknown. Spike it in a non-production environment against both authenticated and unauthenticated endpoints.
- How should I handle laravel-map assets with Vite or after upgrading?
- The package delivers published vendor JavaScript and CSS, so upgrades may require vendor:publish with the force option to refresh assets. Vite users may need to import the vendor CSS and JavaScript explicitly rather than relying on published file paths. After the bundled Leaflet and JS update, confirm the new files land where your layout expects and that only one Leaflet instance loads.
- Is laravel-map production-ready and actively maintained?
- Treat it as single-maintainer risk because the context shows no evidence of tests, CI, or a changelog beyond the four-line release note. Pin a known version and smoke-test map rendering, tile loading, existing markers and layers, and the fetch path. Verify PHP and Laravel constraints before production, and budget time for source review or a fallback to direct Leaflet integration.