nepada / phone-number-input v1.3.1

Phone number form input for Nette forms.

download-cloud-line composer require nepada/phone-number-input

Phone number form input

Build Status Coverage Status Downloads this Month Latest stable


Via Composer:

$ composer require nepada/phone-number-input

Option A: install form container extension method via DI extension

    - Nepada\Bridges\PhoneNumberInputDI\PhoneNumberInputExtension

It will register extension method addPhoneNumber($name, $label = null, ?string $defaultRegionCode = null): PhoneNumberInput to Nette\Forms\Container.

Option B: use trait in your base form/container class

You can also use PhoneNumberInputMixin trait in your base form/container class to add method addPhoneNumber($name, $label = null, ?string $defaultRegionCode = null): PhoneNumberInput.


trait FormControls

    use Nepada\Bridges\PhoneNumberInputForms\PhoneNumberInputMixin;

    public function addContainer($name)
        $control = new Container;
        if ($this->currentGroup !== null) {
        return $this[$name] = $control;


class Container extends Nette\Forms\Container

    use FormControls;


class Form extends Nette\Forms\Form

    use FormControls;



PhoneNumberInput is form control that uses phone number value object to represent its value (see brick/phonenumber for further details). It automatically validates the user input and getValue() method always returns PhoneNumber instance, or null if the input is not filled.

$PhoneNumberInput = $form->addPhoneNumber('phone');
$PhoneNumberInput->setValue('invalid'); // \InvalidArgumentException is thrown
$PhoneNumberInput->setValue('+420 212 345 678'); // the value is internally converted to PhoneNumber value object
$PhoneNumberInput->getValue(); // PhoneNumber instance for +420212345678 


The default validation is fairly lenient - it performs only basic check based on the parsed region and the length of the number.

Strict validation

You can add a more strict validation rule PhoneNumberInput::VALID_STRICT. This rule validates the content against regular expressions from metadata database.

Warning: you must make sure you've got up-to-date metadata library, otherwise you risk running into false positives and false negatives during the validation. The metadata are provided by giggsey/libphonenumber-for-php for backend validation and libphonenumber-js for client side validation.

Region validation

You can restrict the input to accept only numbers from specific region(s):

// Specify one or more ISO 3166-1 alpha-2 country codes
$input->addRule(PhoneNumberInput::REGION, 'Only US phone numbers are allowed', 'US');
$input->addRule(PhoneNumberInput::REGION, 'Only Czech and Slovak phone numbers are allowed', ['CZ', 'SK']);

Default region code

When creating the input you may specify default region code (ISO 3166-1 alpha-2 country code), e.g. $form->addPhoneNumber('phone', 'Phone', 'CZ'). This has two effects:

  1. User may omit the country code prefix for this region in the input field, e.g. 212 345 678 is interpreted as +420 212 345 678.
  2. When rendering the input, phone numbers for this region are displayed in national format instead of international, i.e. the country code is omitted.

Client side validation

This package comes with client side validation built on top of libphonenumber-js. It is published as npm package @nepada/phone-number-input.

libphonenumber-js provides several different metadata sets. You should choose the one based on your validation needs (e.g. if you don't need strict validation, go with min), or build your own custom metadata set.

Using precompiled bundle

Using precompiled bundles is the quick'n'dirty way of getting client side validation to work.

<script src=""></script>
<script src=""></script>
<script src=""></script>
<script src=""></script>
<script src=""></script>

Building your own bundle

It is highly recommended to install the client side package via nmp and compile your own bundle. This way you can use your custom build of metadata set mentioned earlier.

Here is an example script for initialization of phone number input and Nette forms.

import Nette from 'nette-forms';
import initializePhoneNumberInput from '@nepada/phone-number-input';
import metadata from 'libphonenumber-js/metadata.full';
// OR
// import metadata from 'libphonenumber-js/metadata.min';
// OR
// import metadata from 'libphonenumber-js/';
// OR
// import metadata from './metadata.custom.js';

initializePhoneNumberInput(Nette, metadata);
  • v1.3.1 1.3.1

    • Add support for brick/phone-number 0.6.x
  • v1.3.0 1.3.0

    • Drop support for PHP <8.1
    • Use PHP8 native typehints
    • Drop useless annotations
    • PHP 8.3 compatibility
  • v1.2.3 1.2.3

    • Add support for brick/phone-number 0.5.x
  • v1.2.2 1.2.2

    • Support nette/utils 4
  • v1.2.1 1.2.1

    • Restrict maximum supported PHP version in composer.json
    • Update FE build tools
    • PHP 8.2 compatibility
  • v1.2.0 1.2.0

    • PHP 8.1 compatibility.
    • Add support for brick/phone-number 0.3.x and 0.4.x.
  • v1.1.0 1.1.0

    • PHP 8.0 compatibility.
    • JS: nette-forms and libphonenumber-js changed to peerDependencies.
  • v1.0.1 1.0.1

    • Dropped trait prefix:
      • Nepada\Bridges\PhoneNumberInputForms\TPhoneNumberInput is deprecated, use Nepada\Bridges\PhoneNumberInputForms\PhoneNumberInputMixin instead
  • v1.0.0 1.0.0

    • Initial release.






php (>=7.4.0)
brick/phonenumber (^0.2.1@dev)
nette/utils (^3.0@dev)
nette/forms (^3.0@dev)
Componette Componette