npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

zop-react-phone-number-input

v1.0.11

Published

Telephone input for React

Downloads

7

Readme

react-phone-number-input

npm version npm downloads

International phone number <input/> for React (iPhone style).

See Demo

Screenshots

Built-in country <select/> (with autocomplete)

Desktop

Mobile

Native <select/>

Desktop

Mobile

Usage

import Phone from 'react-phone-number-input'

return (
	<Phone
		placeholder="Enter phone number"
		value={ this.state.phone }
		onChange={ phone => this.setState({ phone }) } />
)

The international phone number input utilizes libphonenumber-js international phone number parsing and formatting library.

The phone number <input/> itself is implemented using input-format (which has an issue with some Samsung Android phones, see the workaround).

The countries dropdown with autocomplete is taken from react-responsive-ui.

I could also easily include all country flags in a form of <svg/> React elements as part of this library but the overall size of the bundle would then be about 3 MegaBytes (yeah, those SVGs turned out to be really huge) which is too much for a website. Therefore the default behaviour is a compromise: instead of pleloading the flags for all countries in the expanded list of countries only the flag for the currently selected country is shown. This way the user only downloads a single SVG image and is not forced to download the whole international flags bundle.

CSS

The CSS files for this React component must be included on a page too.

When using Webpack

import 'react-phone-number-input/rrui.css'
import 'react-phone-number-input/style.css'

And set up a postcss-loader with a CSS autoprefixer for supporting old web browsers (e.g. last 2 versions, iOS >= 7, Android >= 4).

When not using Webpack

Get the rrui.css and style.css files from this package, process these files with a CSS autoprefixer for supporting old web browsers (e.g. last 2 versions, iOS >= 7, Android >= 4), and then include them on a page.

<head>
  <link rel="stylesheet" href="/css/react-phone-number-input/rrui.css"/>
  <link rel="stylesheet" href="/css/react-phone-number-input/style.css"/>
</head>

Android

There have been reports of some Samsung Android phones not handling caret positioning properly (e.g. Samsung Galaxy S8+, Samsung Galaxy S7 Edge).

The workaround is to pass smartCaret={false} property:

import Phone from 'react-phone-number-input'

<Phone
  smartCaret={false}
  value={this.state.value}
  onChange={value => this.setState(value)}/>

smartCaret={false} caret is not as "smart" as the default one but still works good enough (and has no issues on Samsung Android phones). When erasing or inserting digits in the middle of a phone number this caret usually jumps to the end: this is the expected behaviour because the "smart" caret positioning has been turned off specifically to fix this Samsung Android phones issue.

Validation

This component is based on libphonenumber-js which is a rewrite of Google's libphonenumber library which doesn't enforce any validation rules when entering phone numbers in "as you type" mode (e.g. when phone number is too long or too short).

For the actual phone number validation use libphonenumber-js: either a loose validation via parseNumber(value) or a strict validation via isValidNumber(value).

Autocomplete

Make sure to wrap a <Phone/> into a <form/> otherwise autocomplete feature won't work: a user will be selecting his phone number from the list but nothing will be happening.

Bug reporting

If you think that the phone number parsing/formatting/validation engine malfunctions for a particular phone number then follow the bug reporting instructions in libphonenumber-js repo.

API

React component

The available props are

  • value — Phone number in E.164 format. E.g. +12223333333 for USA.

  • onChange — Updates the value.

  • country — (optional) The country which is selected by default (can be set after a GeoIP lookup). E.g. US.

  • countries — (optional) Only the specified countries will be selectable. E.g. ['RU', 'KZ', 'UA'].

  • flagsPath — (optional) A base URL path for national flag SVG icons. By default it loads flag icons from flag-icon-css github repo. I imagine someone might want to download those SVG flag icons and host them on their own servers instead.

  • flags — (optional) Supplies <svg/> elements for flags instead of the default <img src="..."/> ones. This might be suitable if someone's making an application which is supposed to be able to work offline (a downloadable app, or an "internal" website): import flags from 'react-phone-number-input/flags'.

  • flagComponent — (optional) A React component for displaying a country flag (replaces the default flag icons).

  • nativeExpanded — If set to true will render native <select/> when country select is expanded instead of the custom one (which has autocomplete feature).

  • displayInitialValueAsLocalNumber — If set to true will display value phone number in local format when the component mounts or when value property is set (see the example on the demo page). The default behaviour is false meaning that if initial value is set then it will be displayed in international format. The reason for such default behaviour is that the newer generation grows up when there are no stationary phones and therefore everyone inputs phone numbers as international ones in their smartphones so people gradually get more accustomed to writing phone numbers in international form rather than in local form.

  • error — a String error message that should be shown.

  • indicateInvaliderror won't be shown unless indicateInvalid is true. The reason for this additional boolean flag is to enable some advanced ("smart") form field error indication scenarios.

For the full list of all possible props see the source code. All other properties are passed through to the <input/> component.

Localization

Country names can be passed via the labels property. E.g. labels={{ RU: 'Россия', US: 'США', ... }}. This component comes pre-packaged with a couple of ready-made translations. Submit pull requests for adding new translations.

import ru from 'react-phone-number-input/locale/ru'

<Phone ... labels={ru}/>

Extensions

Some users asked for phone extension input feature. It can be activated by passing ext property (React.Element). The ext property is most likely gonna be a redux-form <Field/> (or simpler-redux-form <Field/>).

import React, { Component } from 'react'
import { Field, reduxForm } from 'redux-form'
import Phone from 'react-phone-number-input'

@reduxForm({
	form: 'contact'
})
class Form extends Component {
	render() {
		const { handleSubmit } = this.props

		const ext = (
			<Field
				name="ext"
				component="input"
				type="number"
				noValidate
				className={ className } />
		)

		return (
			<form onSubmit={ handleSubmit }>
				<Field
					name="phone"
					component={ Phone }
					ext={ ext } />

				<button type="submit">
					Submit
				</button>
			</form>
		);
	}
}

The code above hasn't been tested, but it most likely works. Phone extension input will appear to the right of the phone number input. One can always skip using ext property and add a completely separate form field for phone number extension input instead.

{ number, ext } object can be converted to RFC3966 string for storing it in a database.

import { formatRFC3966 } from 'libphonenumber-js'

formatRFC3966({ number: '+12133734253', ext: '123' })
// 'tel:+12133734253;ext=123'

Use the accompanying parseRFC3966() function to convert an RFC3966 string into an object having shape { number, ext }.

import { parseRFC3966 } from 'libphonenumber-js'

parseRFC3966('tel:+12133734253;ext=123')
// { number: '+12133734253', ext: '123' }

Reducing bundle size

By default all countries are included which means that libphonenumber-js loads the default metadata having the size of 75 kilobytes. This really isn't much but for those who still want to reduce that to a lesser size there is a special exported <Input/> creator which takes custom metadata as an argument.

For a proper "tree-shaking" bundler that would be

import { Input } from 'react-phone-number-input'
import metadata from './metadata.min.json'

export default function Phone(props) {
	return <Input { ...props } metadata={ metadata }/>
}

And for Common.js environments (or bundlers that can't do proper "tree-shaking") that would be

var Input = require('react-phone-number-input/custom').default
var metadata = require('./metadata.min.json')

module.exports = function Phone(props) {
	return <Input { ...props } metadata={ metadata }/>
}

For generating custom metadata see the guide in libphonenumber-js repo.

Module not found: Error: Can't resolve 'libphonenumber-js/metadata.min'

This error means that your Webpack is misconfigured to exclude .json file extension from the list of the resolved ones. To fix that add it back to resolve.extensions.

{
  resolve: {
    extensions: [".js", ".json", ...]
  }
}

If you're using Webpack 1 then upgrade to a newer version.

License

MIT