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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@inputcn/phone

v0.1.1

Published

Phone number input for React with country selector, live formatting and E.164 output.

Downloads

318

Readme

@inputcn/phone

Searchable country selector, live formatting, E.164 out.

npm license types

Live demo · The contract · All 11 components


Pasting a number that starts with + switches the country and says so, with an undo. The country chip is an ISO code rather than a flag emoji, because Windows ships no glyphs for regional-indicator pairs and a flag degrades to two bare letters there.

Install

Recommended — copy the component source into your project, the way shadcn/ui does:

npx shadcn@latest add https://input-cn.vercel.app/r/phone-input.json

Or install the package and import it directly:

npm i @inputcn/phone

[!NOTE] Either way, import the stylesheet once in your app root:

import "@inputcn/core/styles.css"

Every colour and radius resolves from the shadcn CSS variables you already define, so it matches your theme with no configuration.

Usage

<PhoneInput
  label="Phone number"
  value={phone}        // "+442071234567" — always E.164
  onChange={setPhone}  // never the formatted string
  required
  mobileOnly
  countries={["GB", "US", "IN"]}
/>

[!IMPORTANT] onChange emits the canonical value, never the formatted string.

| Type | Form | Example | |---|---|---| | string | E.164 | "+442071234567" |

Pass name and a hidden input carries that value, so FormData and Server Actions receive it too — with no client component.

What makes it different

  • Trunk prefixes handled. A UK number typed as 020 7123 4567 emits +442071234567. The leading zero is dropped before the length cap, not after.
  • Paste detection. +44 20 7123 4567 sets the value and the country together, and offers an undo.
  • Landline rejection. mobileOnly checks the prefix, so 2071234567 is refused and 7911123456 is not.

Validation

Rules are props. No schema, no resolver, no onBlur handler. Errors stay silent until the first blur, then clear the moment the value becomes valid.

| Prop | Type | Description | |---|---|---| | countries? | readonly string[] | Restrict the selector and reject numbers outside the list. | | mobileOnly? | boolean | Reject numbers that look like landlines. | | defaultCountry? | string | Country selected before the user picks one. Defaults to "US". |

Every error element carries a data-rule attribute naming the rule that failed, so tests assert the rule rather than the sentence.

A matching Zod schema ships from a separate entry point, so Zod never enters your component bundle:

import { phoneSchema } from "@inputcn/phone/schema"

Props

| Prop | Type | Description | |---|---|---| | label? | ReactNode | Visible label. Supply this or aria-label — a field with neither has no accessible name. | | hint? | ReactNode | Helper text under the field. Replaced by the error message while one is showing. | | renderCountry? | (api: {…}) => ReactNode | Override the country trigger and popover. |

Plus the 23 props every inputcn component implements identically — value, onChange, name, required, variant, size and the rest. See the props contract.

[!WARNING] Country data is hand-maintained for 18 countries. Accurate for those, but it is not libphonenumber and does not pretend to be. If you need all 250, wrap this component or open an issue.

Accessibility

Keyboard complete, labelled, and errors announced once through role="alert" rather than on every keystroke. 50 axe-core checks run on every commit.

[!CAUTION] Screen readers have not been verified yet. Until they are, this library is structurally accessible, not screen-reader verified. The full audit, including what is untested and why, is in ACCESSIBILITY.md.


Part of inputcn — the inputs shadcn/ui doesn't ship. Not affiliated with or endorsed by shadcn.