Weave Code
Addressing Laravel Package
markup/addressing
Address management for Laravel: store, format, and validate postal addresses with country and subdivision data, polymorphic address models, and helpers for clean, consistent address handling across your application.
markup/addressing is a Laravel package for storing and working with postal addresses in your applications. It offers a clean, framework-friendly way to attach structured address data to any model while keeping formatting consistent across countries and locales.
- Eloquent-friendly address model and relationships
- Country-aware formatting and validation helpers
- Reusable value objects for address components
- Configurable schema and migrations
- Simple integration with existing Laravel projects
Frequently asked questions about Addressing
- Does markup/addressing work with Laravel 10 and Laravel 11?
- There is no official Laravel integration, so Laravel 10 and 11 compatibility depends entirely on whether the package's 2019-era Composer constraints resolve alongside your PHP and framework versions. The library itself is framework-agnostic PHP, so it will not break Laravel directly, but a stale constraint on commerceguys/addressing is the most likely blocker. Test with composer require markup/addressing on a clean branch and run composer why-not before committing.
- How do I install markup/addressing in a Laravel application?
- Run composer require markup/addressing; there is no service provider to auto-discover and no config file to publish. You will need to write your own singleton binding in a service provider if you want dependency injection. Because the package targets a 2019 dependency set, resolve conflicts against your PHP and Laravel matrix first.
- Is there a Laravel service provider or facade for markup/addressing?
- No. The package ships no service provider, facade, config, migrations, or Blade directives, which keeps it architecturally safe but means you own all the wiring. The usual approach is a thin App\Contracts\AddressFormatter interface bound to a small adapter class. That way the abandoned dependency stays behind a one-file swap.
- What is the difference between markup/addressing and commerceguys/addressing?
- markup/addressing is almost certainly a thin wrapper over commerceguys/addressing, the de-facto PHP implementation of CLDR and UPU address formats. Before adopting it, confirm what it adds beyond calling the upstream library directly. If the delta is a handful of formatting helpers, the extra dependency is not worth the maintenance risk.
- Is markup/addressing still actively maintained?
- No. The last release was 2019-04-15, the repository has one star and zero dependents, and there is no maintainer response path or security disclosure process. Adopting it means adopting the maintenance obligation, including any CVEs inherited from transitive dependencies.
- How do I format a postal address in a Blade template using markup/addressing?
- Treat it as a presentation-layer utility: inject your own AddressFormatter adapter into the controller or view composer, then call it from Blade, API resources, PDF generators, or mail-merge jobs. Avoid calling the library directly inside templates so you can swap the implementation later. The formatting itself is a pure function over a value object, so it is easy to test.
- Does markup/addressing support PHP 8.2 and PHP 8.3?
- Unknown and unlikely to be tested. The package predates PHP 7.4 typed properties and PHP 8 union types, so its own code may run but its dependency constraints are the real question. Verify on PHP 8.2 and 8.3 with a Composer resolution check and run any bundled tests before relying on it.
- Can markup/addressing validate addresses or only format them?
- Its advertised purpose is formatting international postal addresses, and validation is not part of the described scope. Do not assume it validates deliverability, postal code correctness, or subdivision names. If you need validation, pair formatting with a separate validation layer or check whether the upstream library offers it.
- What are the best alternatives to markup/addressing for Laravel?
- Call commerceguys/addressing directly and write the small amount of formatting glue yourself, or use a maintained intl-backed address library. For Laravel apps that only need display formatting, roughly 150 lines behind your own interface often replaces the wrapper entirely. The key criteria are an active release cadence and confirmed PHP 8 support.
- Is markup/addressing safe to use in production?
- Risk is high and concentrated in the supply chain rather than code quality. The package is unmaintained, has effectively one author, ships stale address reference data, and has no CVE remediation path, so silently wrong output is a real failure mode because nothing throws. If you must use it, isolate it behind a first-party interface and be prepared to vendor and self-maintain a fork.
Weaver
How can I help you explore Laravel packages today?