Weave Code
Addressing Bundle Laravel Package
markup/addressing-bundle
Symfony bundle for adding postal addressing to your application: address entities, country and province data, form types, and validation, so you can model, store, and validate addresses without building the fundamentals yourself.
Integration of markup/addressing with Symfony2.
Frequently asked questions about Addressing Bundle
- Is markup/addressing-bundle a Laravel package?
- No. markup/addressing-bundle is a Symfony2 bundle, not a Laravel package. Its value is framework wiring such as bundle registration, a DI extension, a configuration tree, and Symfony service definitions, none of which Laravel uses. The transferable part is the underlying usemarkup/addressing domain library, which should be evaluated separately.
- Can I use markup/addressing-bundle with Laravel 10 or 11?
- It is not recommended. The bundle targets Symfony2, which has been end-of-life for years, so its PHP and Symfony version constraints will almost certainly conflict with Laravel 10 or 11 on PHP 8.1+. Even if Composer resolves it, Laravel has no bundle or container semantics to hook into.
- What does markup/addressing-bundle include?
- It provides Doctrine entities for countries, subdivisions, and postal addresses, along with ISO country and subdivision data with hierarchy. It also includes form types and validators for address input, Twig helpers for formatting addresses and country names, and configurable mappings for existing schemas.
- How do I install markup/addressing-bundle in a Symfony app?
- In a Symfony project you would normally require it with Composer and register the bundle, but this package is tied to Symfony2-era conventions. For a Laravel application, do not install it as an integration path. If you only need addressing logic, evaluate usemarkup/addressing as a plain dependency or consider a maintained alternative.
- Will markup/addressing-bundle conflict with Laravel's Symfony dependencies?
- Likely yes. The bundle is built for Symfony2 container and component versions, while Laravel 10 and 11 ship with much newer Symfony components. That mismatch can produce dependency resolution failures or runtime conflicts, especially on PHP 8.1 and above.
- Should I use usemarkup/addressing directly instead of the bundle?
- Possibly, but only after inspecting it. usemarkup/addressing is the framework-agnostic domain layer, so it is more plausible than the bundle. Check whether it pulls in Symfony components, what PHP versions it supports, and whether it is maintained independently of the bundle.
- Is markup/addressing-bundle still maintained?
- Treat it as abandoned. The last release was 2019-04-09, it has six stars and zero dependents, and there is no evident production usage or community patch path. The evaluation also could not confirm a test suite, so there is little field evidence of correctness.
- What are good alternatives to markup/addressing-bundle for Laravel?
- commerceguys/addressing is the default candidate to evaluate: it is actively maintained, framework-agnostic, and designed for broad locale coverage. Another option is to fork or vendor the specific value objects you need into your own Laravel package and own the maintenance cost.
- Is the country and subdivision data in markup/addressing-bundle up to date?
- Probably not. The bundle is a 2019 snapshot, and postal codes, subdivisions, and country metadata change over time. The evaluation does not identify an update mechanism or external data source, so assume the reference data has decayed.
- Can I fork markup/addressing-bundle under the MIT license?
- Yes. The package is MIT licensed, so forking and vendoring is legally unencumbered. A realistic path is to fork the domain layer, strip Symfony coupling, add tests, and place it under your own namespace, but budget for ongoing address data and code maintenance.
Weaver
How can I help you explore Laravel packages today?