- What is jojostx/filament-tel-input used for?
- It is a FilamentPHP form field for entering international phone numbers. It wraps intl-tel-input to provide a searchable country dropdown with flags and dial codes, automatic formatting, and client-side validation. It fits admin and back-office forms where users need to enter phone numbers consistently, but it should not become a core telephony dependency.
- Which Laravel and Filament versions does filament-tel-input support?
- The package is built for Filament forms, so compatibility depends on the Filament major version used by your application. Verify the Composer constraints in the package's composer.json and README for supported Laravel, PHP, and Filament versions before installing. Pay particular attention to Filament v3 versus v4 support and test against your exact stack.
- How do I install jojostx/filament-tel-input in a Laravel app?
- Install it with Composer using composer require jojostx/filament-tel-input. Then add the field class to a Filament form schema and follow the package README for any asset registration or configuration steps. Because this is a small package, review its source and published assets before using it in a production panel.
- Does filament-tel-input validate and normalize phone numbers to E.164?
- The field uses intl-tel-input for client-side formatting and validation, which helps users enter numbers in an international format. The package assessment notes that server-side normalization to E.164 is not clearly guaranteed, so add your own Laravel validation and normalization before storing values. Do not rely on the browser alone for data quality or compliance.
- Does filament-tel-input work with Livewire and dynamic Filament forms?
- Filament forms run on Livewire, and this package is intended as a Filament form component. Dynamic forms, repeaters, dependent fields, and modal forms can expose state-sync issues, so test those cases in staging. Confirm that the selected country and formatted number hydrate and dehydrate correctly in your Livewire version.
- How are intl-tel-input assets loaded under Vite or a strict CSP?
- The package depends on client-side JavaScript and CSS for intl-tel-input, so asset loading must work with your Filament asset pipeline. If you use Vite or a strict Content Security Policy, verify script and style sources, nonce handling, and whether assets are published or injected. Test the field in a staging environment that matches production CSP settings.
- Are country flags and dial code data updated automatically?
- Country metadata typically comes from the bundled intl-tel-input library or its utilities, so freshness depends on the package version and upstream updates. Check how the country dataset is shipped and whether updates require a Composer update or asset republish. If accurate global dialing data is business-critical, monitor upstream releases and have a refresh plan.
- Is jojostx/filament-tel-input production-ready and well maintained?
- The package has low visible adoption, with only a few stars and no dependents noted in the assessment. That does not make it unusable, but it should be treated as a small external dependency rather than a strategic platform component. Pin the version, review the source, assign an internal owner, and pilot it in a low-risk form first.
- What are alternatives to filament-tel-input for Laravel phone validation?
- A common alternative is a native Filament TextInput combined with a server-side library such as libphonenumber-for-php for validation and E.164 normalization. You can also build a project-owned custom field that wraps the JavaScript phone input of your choice. If your application is not already using Filament, adopting this package is not a good reason to introduce Filament.
- How should I test and fall back if filament-tel-input breaks after a Filament upgrade?
- Pin the package version and add feature or browser tests that cover phone entry, country selection, validation messages, and stored formats. Isolate the field behind a project-owned adapter or custom form component so you can replace it with a native TextInput and server-side validation without rewriting every form. Before any Filament upgrade, explicitly verify compatibility and keep a tested fallback path.