Weave Code
Phone Number Advanced Laravel Package
gepur-it/phone-number-advanced
A Laravel package for advanced phone number handling, with parsing, formatting, validation, and country-aware utilities to keep numbers consistent across your app. Integrates with Eloquent models and Blade views for cleaner input and display.
Phone number type
Frequently asked questions about Phone Number Advanced
- How do I install gepur-it/phone-number-advanced in a Laravel app?
- Install it with Composer using composer require gepur-it/phone-number-advanced, then confirm the service provider is registered through Laravel package auto-discovery. Because the published documentation is thin, verify any config merge or publishable config file by inspecting the package's service provider directly. After install, run a quick smoke test in tinker to confirm the parsing and formatting API resolves from the container before wiring it into application code.
- Does gepur-it/phone-number-advanced support PHP 8, Laravel 10, or Laravel 11?
- Version 5.3.0 includes a release note stating PHP 8 support was updated, which makes PHP 8 installs plausible, but that note does not document which PHP 8.x minors or which Laravel versions are actually supported. Check the composer.json require constraints on the exact tag you intend to install rather than assuming compatibility from the release note. If your application runs Laravel 10 or 11 on PHP 8.2 or newer, treat compatibility as unproven and validate it in a time-boxed spike before adoption.
- How do I format a phone number as E.164, national, or RFC3966 with this Laravel package?
- The package exposes a fluent, chainable API for parsing a raw input string and then rendering it in E.164, national, or RFC3966 format. In practice you parse the number once, keep the parsed object, and call the appropriate format method at the boundary where you need the output. Always store the canonical E.164 value and only convert to national or RFC3966 for display, exports, or click-to-call links.
- Can I use gepur-it/phone-number-advanced for Laravel validation rules on phone numbers?
- The package advertises integration with Laravel's validation rules and country-aware validation, so you can validate input inside Form Requests and validators instead of writing custom regexes. Because validation and formatting behavior may have shifted in v5.3.0, add regression tests covering the number formats and countries your app actually accepts. If validation quality is critical, wrap the rule in your own custom rule class so you can swap the underlying implementation later.
- How do I detect the country from an international phone number?
- Country detection works from a parsed number, so pass a value that includes the international dialing prefix, such as an E.164 string, rather than a locally formatted number. The detected region can then drive per-country validation rules, default formatting, or routing logic. Test detection against the specific countries in your user base, since country metadata can become stale between package releases.
- How should I store phone numbers in the database with Eloquent to keep them consistent?
- Normalize to E.164 before the value is persisted, for example inside a mutator, a model observer, or a dedicated form request, and keep a separate column or accessor for the original raw input if you need an audit trail. This keeps joins, de-duplication, and SMS sending predictable regardless of how users typed the number. Store the country code or detected region alongside the E.164 value when your product logic depends on it.
- How do I display formatted phone numbers in Blade views?
- Format the number in your model accessor or a small presenter, then pass the already-formatted string into the Blade view rather than calling parsing logic inside the template. The package is described as integrating with Blade for cleaner input and display, so you can also format directly with its fluent API if you prefer. Keeping formatting out of the template makes it easy to switch between national and E.164 output per context, such as UI versus exports.
- Is gepur-it/phone-number-advanced safe for production checkout, KYC, or SMS delivery flows?
- Treat it as high risk for revenue-critical paths at this stage. It is a low-adoption utility package, and a single v5.3.0 release does not prove an active maintenance cadence or broad ecosystem validation. If you need it, wrap it behind an internal PhoneNumberService or custom validation rule and cover it with contract tests, so it can be replaced without touching domain code. Avoid making it the sole gatekeeper for checkout, identity verification, or messaging deliverability.
- Does this package wrap libphonenumber or implement its own phone parsing and country metadata?
- The published overview does not state whether it wraps a maintained library such as libphonenumber or implements parsing and validation itself, and the v5.3.0 release note is too sparse to answer that. Inspect composer.json and the source to confirm, because it determines how stale country plans and number metadata can become. If it bundles its own metadata, plan periodic refreshes or a fork, since numbering plans change over time.
- What are the alternatives if I need a better-maintained Laravel phone number package?
- The safest baseline is giggsey/libphonenumber-for-php, the PHP port of Google's libphonenumber, which has strong upkeep and regular metadata updates, optionally paired with a thin Laravel wrapper you control. You can also implement a small internal PhoneNumberService that delegates to libphonenumber directly and exposes the same parse, format, and validate methods you would have used here. Because this package is MIT licensed, you can also fork or vendor v5.3.0 and patch it yourself, but budget for ongoing compatibility and metadata maintenance if you do.
Weaver
How can I help you explore Laravel packages today?