- Is padam87/address-bundle a Laravel package?
- No. It is a Symfony bundle built around Doctrine ORM entities and Symfony form types. It ships no Laravel service provider, config publishables, or Eloquent models, so you cannot treat it as a Laravel-native dependency.
- Can I install padam87/address-bundle in a Laravel app with Composer?
- Not realistically. Its Composer constraints target Symfony 2.x/3.x-era components and an old Guzzle/Geocoder stack, while Laravel 10/11/12 run Symfony 6/7 components, causing solver conflicts. There is also no bundle registration or auto-discovery path in Laravel.
- What Laravel versions does padam87/address-bundle support?
- None. The package is a Symfony bundle last released in 2016 and has no Laravel version support matrix. Its Symfony constraints predate modern Laravel's Symfony component requirements.
- What features does padam87/address-bundle actually provide?
- It provides a Doctrine-backed Address entity with structured postal components and country/region data, Symfony form types for address input, a formatter for locale-aware address strings, and a geocoder service. The reusable ideas are address storage, formatting, and geocoding. The code itself is Symfony and Doctrine-bound.
- How do I port the address entity to Laravel Eloquent?
- Create an addresses table migration and an Address Eloquent model. Map structured components to columns or JSON casts, store coordinates with a custom cast, and replace Doctrine lifecycle callbacks with model events or observers. Add Form Request validation for postal_code and country-aware rules.
- How should I handle address formatting in Laravel?
- Use an AddressFormatter contract with per-locale strategy classes instead of copying the bundle's templates. For country and administrative data, prefer maintained libraries such as commerceguys/addressing or symfony/intl. The bundle's 2016 formatting templates are likely stale for APAC and LATAM locales.
- Does the bundle handle geocoding, and how do I replace it in Laravel?
- It includes a geocoder service that resolves an address to latitude and longitude through an injected geocoder client. In Laravel, define a Geocoder contract, add provider adapters, wrap calls with Cache::remember, and dispatch a queued GeocodeAddress job with retries. Build against a maintained client from day one instead of porting the old provider parsing.
- Is padam87/address-bundle maintained and safe for production?
- No. Last release was 2016-11-15, with roughly nine years without PHP 8.x work, security triage, or issue response. It has about 10 stars and zero dependents, so there is little community validation. The MIT license is clean, but maintenance risk is high.
- What are good alternatives to padam87/address-bundle for Laravel?
- For formatting and country data, evaluate commerceguys/addressing or symfony/intl. For geocoding, use maintained geocoder-php clients behind your own contract and cache. For storage, build a small Eloquent address model with validation rather than installing an abandoned Symfony bundle.
- When would it still make sense to use padam87/address-bundle?
- Only as a design reference when you need a quick model for structured addresses, formatting, and geocoding responsibilities. Treat it as source material to port, not a runtime dependency. If you need a maintained Symfony solution, look for current Symfony address or form packages.