@webority-technologies/mobile-core 0.0.3 → 0.0.4

package/lib/commonjs/formatters/phone.js

@@ -8,31 +8,37 @@ exports.formatPhone = formatPhone;
 Object.defineProperty(exports, "isValidPhoneNumber", {
   enumerable: true,
   get: function () {
-    return _libphonenumberJs.isValidPhoneNumber;
+    return _max.isValidPhoneNumber;
   }
 });
 exports.normalizePhone = void 0;
 Object.defineProperty(exports, "parsePhoneNumber", {
   enumerable: true,
   get: function () {
-    return _libphonenumberJs.parsePhoneNumber;
+    return _max.parsePhoneNumber;
   }
 });
 Object.defineProperty(exports, "parsePhoneNumberFromString", {
   enumerable: true,
   get: function () {
-    return _libphonenumberJs.parsePhoneNumberFromString;
+    return _max.parsePhoneNumberFromString;
   }
 });
-var _libphonenumberJs = require("libphonenumber-js");
+var _max = require("libphonenumber-js/max");
 /**
- * Real cross-country validation, re-exported rather than reimplemented.
- * formatPhone/normalizePhone/detectPhoneCountry below are a fast, dependency-
- * light DISPLAY formatter for a fixed set of countries; they are not a
- * validator. Real phone number plans have country-specific area-code and
- * mobile-prefix rules that only a maintained metadata table gets right -
- * hand-rolling that risks silently-wrong validation for a country nobody
- * tests against. Both live here so consumers get one phone module, not two.
+ * The bare 'libphonenumber-js' entry point actually resolves to the library's
+ * OWN slimmed-down min/ metadata internally, not its full data - './max' is
+ * the variant with complete per-country metadata. Since the reason this
+ * module exists is validation and formatting accuracy, the more accurate
+ * variant wins throughout this file, not just for validation.
+ */
+
+/**
+ * Re-exported under our own name rather than importing CountryCode directly
+ * everywhere, so a future need to diverge (or re-narrow) has one place to do
+ * it. Every ISO 3166-1 alpha-2 code libphonenumber-js recognises - formatPhone
+ * and detectPhoneCountry below are genuinely correct for all of them, not a
+ * curated subset.
  */
 
 /**
@@ -47,82 +53,32 @@ const normalizePhone = input => {
   const digits = trimmed.replace(/\D/g, '');
   return hasPlus ? `+${digits}` : digits;
 };
-exports.normalizePhone = normalizePhone;
-const groupIndianMobile = digits => {
-  // Indian mobile is 10 digits: format as `XXXXX XXXXX`.
-  if (digits.length !== 10) {
-    return digits;
-  }
-  return `${digits.slice(0, 5)} ${digits.slice(5)}`;
-};
-
-// Longest calling code first so a 3-digit code is never shadowed by a shorter one.
-const COUNTRY_RULES = [{
-  country: 'AE',
-  callingCode: '971',
-  nationalLength: 9,
-  group: n => `${n.slice(0, 2)} ${n.slice(2, 5)} ${n.slice(5)}`
-}, {
-  country: 'IN',
-  callingCode: '91',
-  nationalLength: 10,
-  group: groupIndianMobile
-}, {
-  country: 'GB',
-  callingCode: '44',
-  nationalLength: 10,
-  group: n => `${n.slice(0, 4)} ${n.slice(4, 7)} ${n.slice(7)}`
-}, {
-  country: 'AU',
-  callingCode: '61',
-  nationalLength: 9,
-  group: n => `${n.slice(0, 3)} ${n.slice(3, 6)} ${n.slice(6)}`
-}, {
-  country: 'SG',
-  callingCode: '65',
-  nationalLength: 8,
-  group: n => `${n.slice(0, 4)} ${n.slice(4)}`
-}, {
-  country: 'US',
-  callingCode: '1',
-  nationalLength: 10,
-  group: n => `(${n.slice(0, 3)}) ${n.slice(3, 6)}-${n.slice(6)}`
-},
-// US and CA share a calling code and are indistinguishable from it alone;
-// this row only serves an explicit `country: 'CA'` override, never detection
-// (it sits after the US row, and findRuleByCallingCode returns the first match).
-{
-  country: 'CA',
-  callingCode: '1',
-  nationalLength: 10,
-  group: n => `(${n.slice(0, 3)}) ${n.slice(3, 6)}-${n.slice(6)}`
-}];
-const findRuleByCallingCode = rest => COUNTRY_RULES.find(rule => rest.startsWith(rule.callingCode));
-const findRuleByCountry = country => COUNTRY_RULES.find(rule => rule.country === country);
 
 /**
  * Detect the country of a phone number: from its own `+` country code when
  * present, otherwise from `defaultCountryCode`. Returns null when neither
- * carries a recognised calling code.
+ * parses to a recognised country.
  */
+exports.normalizePhone = normalizePhone;
 const detectPhoneCountry = (input, defaultCountryCode = '+91') => {
   const normalized = normalizePhone(input);
   if (!normalized) {
     return null;
   }
   if (normalized.startsWith('+')) {
-    return findRuleByCallingCode(normalized.slice(1))?.country ?? null;
+    return (0, _max.parsePhoneNumberFromString)(normalized)?.country ?? null;
   }
   const normalizedDefault = normalizePhone(defaultCountryCode);
   if (!normalizedDefault.startsWith('+')) {
     return null;
   }
-  return findRuleByCallingCode(normalizedDefault.slice(1))?.country ?? null;
+  return (0, _max.parsePhoneNumberFromString)(normalizedDefault + normalized)?.country ?? null;
 };
 exports.detectPhoneCountry = detectPhoneCountry;
 const bestEffortGroup = rest => {
-  // No known country code matched (or matched but the wrong length): split
-  // the country code (first 1-3 digits) and group the rest in 4s.
+  // Not a parseable number at all (garbage input, or a real number that's an
+  // unsupported length for its country): split the country code (first 1-3
+  // digits) and group the rest in 4s, rather than returning nothing.
   const ccLen = rest.length > 11 ? 3 : rest.length > 10 ? 2 : 1;
   const cc = rest.slice(0, ccLen);
   const number = rest.slice(ccLen);
@@ -131,13 +87,18 @@ const bestEffortGroup = rest => {
 };
 
 /**
- * Format a phone number for human display.
+ * Format a phone number for human display, via libphonenumber-js's own
+ * per-country formatting rather than a hand-rolled grouping table - correct
+ * for every country it recognises, not a curated subset.
  *
- * - Indian mobile (10 digits) → `XXXXX XXXXX`
- * - With `+91` country code → `+91 XXXXX XXXXX`
- * - A number that already carries a recognised country code is grouped for
- *   that country regardless of `defaultCountryCode`.
- * - Other inputs are returned as `+CC NNNN NNNN…` best-effort grouping.
+ * - A number that already carries a `+` country code formats for that country.
+ * - A bare national number formats for `options.country` when given, else for
+ *   the country implied by `defaultCountryCode` (default `+91`).
+ * - `includeCountryCode` controls international vs national format; defaults
+ *   to international whenever the country was detected rather than passed in
+ *   explicitly as `options.country`, and to national when it was.
+ * - Input libphonenumber-js can't parse into a valid number for the resolved
+ *   country falls back to a best-effort `+CC NNNN NNNN…` digit grouping.
  */
 
 function formatPhone(input, arg) {
@@ -150,35 +111,40 @@ function formatPhone(input, arg) {
   }
   const options = typeof arg === 'string' ? {} : arg ?? {};
   const defaultCountryCode = typeof arg === 'string' ? arg : options.defaultCountryCode ?? '+91';
-  if (normalized.startsWith('+')) {
-    const rest = normalized.slice(1);
-    const detectedRule = findRuleByCallingCode(rest);
-    const activeRule = options.country ? findRuleByCountry(options.country) : detectedRule;
-    if (activeRule) {
-      const national = detectedRule ? rest.slice(detectedRule.callingCode.length) : rest;
-      if (national.length === activeRule.nationalLength) {
-        const includeCc = options.includeCountryCode ?? true;
-        const body = activeRule.group(national);
-        return includeCc ? `+${activeRule.callingCode} ${body}` : body;
-      }
-    }
-    return bestEffortGroup(rest);
-  }
+  const hasOwnCountryCode = normalized.startsWith('+');
+  let parsed;
+  // What to best-effort group if parsing fails to produce a valid number.
+  // Defaults to the plain input; the defaultCountryCode branch below points
+  // it at the combined digits instead, so a bare number that turns out
+  // invalid for its detected country still shows that country's code rather
+  // than silently discarding it.
+  let fallbackRest = normalized;
   if (options.country) {
-    const rule = findRuleByCountry(options.country);
-    if (rule && normalized.length === rule.nationalLength) {
-      const includeCc = options.includeCountryCode ?? false;
-      const body = rule.group(normalized);
-      return includeCc ? `+${rule.callingCode} ${body}` : body;
+    // parsePhoneNumberFromString ignores this hint when normalized already
+    // carries its own +, so a real E.164 number is never overridden by a
+    // wrong or stale options.country.
+    parsed = (0, _max.parsePhoneNumberFromString)(normalized, options.country);
+  } else if (hasOwnCountryCode) {
+    parsed = (0, _max.parsePhoneNumberFromString)(normalized);
+  } else {
+    const normalizedDefault = normalizePhone(defaultCountryCode);
+    if (normalizedDefault.startsWith('+')) {
+      const combined = normalizedDefault + normalized;
+      parsed = (0, _max.parsePhoneNumberFromString)(combined);
+      fallbackRest = combined;
+    } else {
+      parsed = undefined;
     }
-    return normalized.replace(/(.{4})(?=.)/g, '$1 ').trim();
   }
 
-  // No country code; assume default if length matches Indian mobile.
-  if (normalized.length === 10) {
-    return `${defaultCountryCode} ${groupIndianMobile(normalized)}`;
+  // International by default whenever the country came from the number
+  // itself (or from defaultCountryCode); national by default only when a
+  // bare number relied on an explicit options.country to resolve at all.
+  const includeCcDefault = hasOwnCountryCode || !options.country;
+  if (parsed?.isValid()) {
+    const includeCc = options.includeCountryCode ?? includeCcDefault;
+    return includeCc ? parsed.formatInternational() : parsed.formatNational();
   }
-  // Otherwise just return groups of 4.
-  return normalized.replace(/(.{4})(?=.)/g, '$1 ').trim();
+  return fallbackRest.startsWith('+') ? bestEffortGroup(fallbackRest.slice(1)) : fallbackRest.replace(/(.{4})(?=.)/g, '$1 ').trim();
 }
 //# sourceMappingURL=phone.js.map

package/lib/module/formatters/phone.js

@@ -1,16 +1,23 @@
 "use strict";
 
 /**
- * Real cross-country validation, re-exported rather than reimplemented.
- * formatPhone/normalizePhone/detectPhoneCountry below are a fast, dependency-
- * light DISPLAY formatter for a fixed set of countries; they are not a
- * validator. Real phone number plans have country-specific area-code and
- * mobile-prefix rules that only a maintained metadata table gets right -
- * hand-rolling that risks silently-wrong validation for a country nobody
- * tests against. Both live here so consumers get one phone module, not two.
+ * The bare 'libphonenumber-js' entry point actually resolves to the library's
+ * OWN slimmed-down min/ metadata internally, not its full data - './max' is
+ * the variant with complete per-country metadata. Since the reason this
+ * module exists is validation and formatting accuracy, the more accurate
+ * variant wins throughout this file, not just for validation.
+ */
+import { parsePhoneNumberFromString } from 'libphonenumber-js/max';
+export { isValidPhoneNumber, parsePhoneNumber, parsePhoneNumberFromString } from 'libphonenumber-js/max';
+
+/**
+ * Re-exported under our own name rather than importing CountryCode directly
+ * everywhere, so a future need to diverge (or re-narrow) has one place to do
+ * it. Every ISO 3166-1 alpha-2 code libphonenumber-js recognises - formatPhone
+ * and detectPhoneCountry below are genuinely correct for all of them, not a
+ * curated subset.
  */
 
-export { isValidPhoneNumber, parsePhoneNumber, parsePhoneNumberFromString } from 'libphonenumber-js';
 /**
  * Strip everything except digits and a leading `+` (preserved if present).
  */
@@ -23,62 +30,11 @@ export const normalizePhone = input => {
   const digits = trimmed.replace(/\D/g, '');
   return hasPlus ? `+${digits}` : digits;
 };
-const groupIndianMobile = digits => {
-  // Indian mobile is 10 digits: format as `XXXXX XXXXX`.
-  if (digits.length !== 10) {
-    return digits;
-  }
-  return `${digits.slice(0, 5)} ${digits.slice(5)}`;
-};
-
-// Longest calling code first so a 3-digit code is never shadowed by a shorter one.
-const COUNTRY_RULES = [{
-  country: 'AE',
-  callingCode: '971',
-  nationalLength: 9,
-  group: n => `${n.slice(0, 2)} ${n.slice(2, 5)} ${n.slice(5)}`
-}, {
-  country: 'IN',
-  callingCode: '91',
-  nationalLength: 10,
-  group: groupIndianMobile
-}, {
-  country: 'GB',
-  callingCode: '44',
-  nationalLength: 10,
-  group: n => `${n.slice(0, 4)} ${n.slice(4, 7)} ${n.slice(7)}`
-}, {
-  country: 'AU',
-  callingCode: '61',
-  nationalLength: 9,
-  group: n => `${n.slice(0, 3)} ${n.slice(3, 6)} ${n.slice(6)}`
-}, {
-  country: 'SG',
-  callingCode: '65',
-  nationalLength: 8,
-  group: n => `${n.slice(0, 4)} ${n.slice(4)}`
-}, {
-  country: 'US',
-  callingCode: '1',
-  nationalLength: 10,
-  group: n => `(${n.slice(0, 3)}) ${n.slice(3, 6)}-${n.slice(6)}`
-},
-// US and CA share a calling code and are indistinguishable from it alone;
-// this row only serves an explicit `country: 'CA'` override, never detection
-// (it sits after the US row, and findRuleByCallingCode returns the first match).
-{
-  country: 'CA',
-  callingCode: '1',
-  nationalLength: 10,
-  group: n => `(${n.slice(0, 3)}) ${n.slice(3, 6)}-${n.slice(6)}`
-}];
-const findRuleByCallingCode = rest => COUNTRY_RULES.find(rule => rest.startsWith(rule.callingCode));
-const findRuleByCountry = country => COUNTRY_RULES.find(rule => rule.country === country);
 
 /**
  * Detect the country of a phone number: from its own `+` country code when
  * present, otherwise from `defaultCountryCode`. Returns null when neither
- * carries a recognised calling code.
+ * parses to a recognised country.
  */
 export const detectPhoneCountry = (input, defaultCountryCode = '+91') => {
   const normalized = normalizePhone(input);
@@ -86,17 +42,18 @@ export const detectPhoneCountry = (input, defaultCountryCode = '+91') => {
     return null;
   }
   if (normalized.startsWith('+')) {
-    return findRuleByCallingCode(normalized.slice(1))?.country ?? null;
+    return parsePhoneNumberFromString(normalized)?.country ?? null;
   }
   const normalizedDefault = normalizePhone(defaultCountryCode);
   if (!normalizedDefault.startsWith('+')) {
     return null;
   }
-  return findRuleByCallingCode(normalizedDefault.slice(1))?.country ?? null;
+  return parsePhoneNumberFromString(normalizedDefault + normalized)?.country ?? null;
 };
 const bestEffortGroup = rest => {
-  // No known country code matched (or matched but the wrong length): split
-  // the country code (first 1-3 digits) and group the rest in 4s.
+  // Not a parseable number at all (garbage input, or a real number that's an
+  // unsupported length for its country): split the country code (first 1-3
+  // digits) and group the rest in 4s, rather than returning nothing.
   const ccLen = rest.length > 11 ? 3 : rest.length > 10 ? 2 : 1;
   const cc = rest.slice(0, ccLen);
   const number = rest.slice(ccLen);
@@ -105,13 +62,18 @@ const bestEffortGroup = rest => {
 };
 
 /**
- * Format a phone number for human display.
+ * Format a phone number for human display, via libphonenumber-js's own
+ * per-country formatting rather than a hand-rolled grouping table - correct
+ * for every country it recognises, not a curated subset.
  *
- * - Indian mobile (10 digits) → `XXXXX XXXXX`
- * - With `+91` country code → `+91 XXXXX XXXXX`
- * - A number that already carries a recognised country code is grouped for
- *   that country regardless of `defaultCountryCode`.
- * - Other inputs are returned as `+CC NNNN NNNN…` best-effort grouping.
+ * - A number that already carries a `+` country code formats for that country.
+ * - A bare national number formats for `options.country` when given, else for
+ *   the country implied by `defaultCountryCode` (default `+91`).
+ * - `includeCountryCode` controls international vs national format; defaults
+ *   to international whenever the country was detected rather than passed in
+ *   explicitly as `options.country`, and to national when it was.
+ * - Input libphonenumber-js can't parse into a valid number for the resolved
+ *   country falls back to a best-effort `+CC NNNN NNNN…` digit grouping.
  */
 
 export function formatPhone(input, arg) {
@@ -124,35 +86,40 @@ export function formatPhone(input, arg) {
   }
   const options = typeof arg === 'string' ? {} : arg ?? {};
   const defaultCountryCode = typeof arg === 'string' ? arg : options.defaultCountryCode ?? '+91';
-  if (normalized.startsWith('+')) {
-    const rest = normalized.slice(1);
-    const detectedRule = findRuleByCallingCode(rest);
-    const activeRule = options.country ? findRuleByCountry(options.country) : detectedRule;
-    if (activeRule) {
-      const national = detectedRule ? rest.slice(detectedRule.callingCode.length) : rest;
-      if (national.length === activeRule.nationalLength) {
-        const includeCc = options.includeCountryCode ?? true;
-        const body = activeRule.group(national);
-        return includeCc ? `+${activeRule.callingCode} ${body}` : body;
-      }
-    }
-    return bestEffortGroup(rest);
-  }
+  const hasOwnCountryCode = normalized.startsWith('+');
+  let parsed;
+  // What to best-effort group if parsing fails to produce a valid number.
+  // Defaults to the plain input; the defaultCountryCode branch below points
+  // it at the combined digits instead, so a bare number that turns out
+  // invalid for its detected country still shows that country's code rather
+  // than silently discarding it.
+  let fallbackRest = normalized;
   if (options.country) {
-    const rule = findRuleByCountry(options.country);
-    if (rule && normalized.length === rule.nationalLength) {
-      const includeCc = options.includeCountryCode ?? false;
-      const body = rule.group(normalized);
-      return includeCc ? `+${rule.callingCode} ${body}` : body;
+    // parsePhoneNumberFromString ignores this hint when normalized already
+    // carries its own +, so a real E.164 number is never overridden by a
+    // wrong or stale options.country.
+    parsed = parsePhoneNumberFromString(normalized, options.country);
+  } else if (hasOwnCountryCode) {
+    parsed = parsePhoneNumberFromString(normalized);
+  } else {
+    const normalizedDefault = normalizePhone(defaultCountryCode);
+    if (normalizedDefault.startsWith('+')) {
+      const combined = normalizedDefault + normalized;
+      parsed = parsePhoneNumberFromString(combined);
+      fallbackRest = combined;
+    } else {
+      parsed = undefined;
     }
-    return normalized.replace(/(.{4})(?=.)/g, '$1 ').trim();
   }
 
-  // No country code; assume default if length matches Indian mobile.
-  if (normalized.length === 10) {
-    return `${defaultCountryCode} ${groupIndianMobile(normalized)}`;
+  // International by default whenever the country came from the number
+  // itself (or from defaultCountryCode); national by default only when a
+  // bare number relied on an explicit options.country to resolve at all.
+  const includeCcDefault = hasOwnCountryCode || !options.country;
+  if (parsed?.isValid()) {
+    const includeCc = options.includeCountryCode ?? includeCcDefault;
+    return includeCc ? parsed.formatInternational() : parsed.formatNational();
   }
-  // Otherwise just return groups of 4.
-  return normalized.replace(/(.{4})(?=.)/g, '$1 ').trim();
+  return fallbackRest.startsWith('+') ? bestEffortGroup(fallbackRest.slice(1)) : fallbackRest.replace(/(.{4})(?=.)/g, '$1 ').trim();
 }
 //# sourceMappingURL=phone.js.map

package/lib/typescript/commonjs/formatters/phone.d.ts

@@ -1,15 +1,21 @@
 /**
- * Real cross-country validation, re-exported rather than reimplemented.
- * formatPhone/normalizePhone/detectPhoneCountry below are a fast, dependency-
- * light DISPLAY formatter for a fixed set of countries; they are not a
- * validator. Real phone number plans have country-specific area-code and
- * mobile-prefix rules that only a maintained metadata table gets right -
- * hand-rolling that risks silently-wrong validation for a country nobody
- * tests against. Both live here so consumers get one phone module, not two.
+ * The bare 'libphonenumber-js' entry point actually resolves to the library's
+ * OWN slimmed-down min/ metadata internally, not its full data - './max' is
+ * the variant with complete per-country metadata. Since the reason this
+ * module exists is validation and formatting accuracy, the more accurate
+ * variant wins throughout this file, not just for validation.
  */
-export type { PhoneNumber } from 'libphonenumber-js';
-export { isValidPhoneNumber, parsePhoneNumber, parsePhoneNumberFromString } from 'libphonenumber-js';
-export type PhoneCountry = 'IN' | 'US' | 'GB' | 'AE' | 'AU' | 'SG' | 'CA';
+import { type CountryCode } from 'libphonenumber-js/max';
+export type { PhoneNumber } from 'libphonenumber-js/max';
+export { isValidPhoneNumber, parsePhoneNumber, parsePhoneNumberFromString } from 'libphonenumber-js/max';
+/**
+ * Re-exported under our own name rather than importing CountryCode directly
+ * everywhere, so a future need to diverge (or re-narrow) has one place to do
+ * it. Every ISO 3166-1 alpha-2 code libphonenumber-js recognises - formatPhone
+ * and detectPhoneCountry below are genuinely correct for all of them, not a
+ * curated subset.
+ */
+export type PhoneCountry = CountryCode;
 export interface FormatPhoneOptions {
     defaultCountryCode?: string;
     country?: PhoneCountry;
@@ -22,17 +28,22 @@ export declare const normalizePhone: (input: string) => string;
 /**
  * Detect the country of a phone number: from its own `+` country code when
  * present, otherwise from `defaultCountryCode`. Returns null when neither
- * carries a recognised calling code.
+ * parses to a recognised country.
  */
 export declare const detectPhoneCountry: (input: string, defaultCountryCode?: string) => PhoneCountry | null;
 /**
- * Format a phone number for human display.
+ * Format a phone number for human display, via libphonenumber-js's own
+ * per-country formatting rather than a hand-rolled grouping table - correct
+ * for every country it recognises, not a curated subset.
  *
- * - Indian mobile (10 digits) → `XXXXX XXXXX`
- * - With `+91` country code → `+91 XXXXX XXXXX`
- * - A number that already carries a recognised country code is grouped for
- *   that country regardless of `defaultCountryCode`.
- * - Other inputs are returned as `+CC NNNN NNNN…` best-effort grouping.
+ * - A number that already carries a `+` country code formats for that country.
+ * - A bare national number formats for `options.country` when given, else for
+ *   the country implied by `defaultCountryCode` (default `+91`).
+ * - `includeCountryCode` controls international vs national format; defaults
+ *   to international whenever the country was detected rather than passed in
+ *   explicitly as `options.country`, and to national when it was.
+ * - Input libphonenumber-js can't parse into a valid number for the resolved
+ *   country falls back to a best-effort `+CC NNNN NNNN…` digit grouping.
  */
 export declare function formatPhone(input: string, defaultCountryCode?: string): string;
 export declare function formatPhone(input: string, options?: FormatPhoneOptions): string;

package/lib/typescript/module/formatters/phone.d.ts

@@ -1,15 +1,21 @@
 /**
- * Real cross-country validation, re-exported rather than reimplemented.
- * formatPhone/normalizePhone/detectPhoneCountry below are a fast, dependency-
- * light DISPLAY formatter for a fixed set of countries; they are not a
- * validator. Real phone number plans have country-specific area-code and
- * mobile-prefix rules that only a maintained metadata table gets right -
- * hand-rolling that risks silently-wrong validation for a country nobody
- * tests against. Both live here so consumers get one phone module, not two.
+ * The bare 'libphonenumber-js' entry point actually resolves to the library's
+ * OWN slimmed-down min/ metadata internally, not its full data - './max' is
+ * the variant with complete per-country metadata. Since the reason this
+ * module exists is validation and formatting accuracy, the more accurate
+ * variant wins throughout this file, not just for validation.
  */
-export type { PhoneNumber } from 'libphonenumber-js';
-export { isValidPhoneNumber, parsePhoneNumber, parsePhoneNumberFromString } from 'libphonenumber-js';
-export type PhoneCountry = 'IN' | 'US' | 'GB' | 'AE' | 'AU' | 'SG' | 'CA';
+import { type CountryCode } from 'libphonenumber-js/max';
+export type { PhoneNumber } from 'libphonenumber-js/max';
+export { isValidPhoneNumber, parsePhoneNumber, parsePhoneNumberFromString } from 'libphonenumber-js/max';
+/**
+ * Re-exported under our own name rather than importing CountryCode directly
+ * everywhere, so a future need to diverge (or re-narrow) has one place to do
+ * it. Every ISO 3166-1 alpha-2 code libphonenumber-js recognises - formatPhone
+ * and detectPhoneCountry below are genuinely correct for all of them, not a
+ * curated subset.
+ */
+export type PhoneCountry = CountryCode;
 export interface FormatPhoneOptions {
     defaultCountryCode?: string;
     country?: PhoneCountry;
@@ -22,17 +28,22 @@ export declare const normalizePhone: (input: string) => string;
 /**
  * Detect the country of a phone number: from its own `+` country code when
  * present, otherwise from `defaultCountryCode`. Returns null when neither
- * carries a recognised calling code.
+ * parses to a recognised country.
  */
 export declare const detectPhoneCountry: (input: string, defaultCountryCode?: string) => PhoneCountry | null;
 /**
- * Format a phone number for human display.
+ * Format a phone number for human display, via libphonenumber-js's own
+ * per-country formatting rather than a hand-rolled grouping table - correct
+ * for every country it recognises, not a curated subset.
  *
- * - Indian mobile (10 digits) → `XXXXX XXXXX`
- * - With `+91` country code → `+91 XXXXX XXXXX`
- * - A number that already carries a recognised country code is grouped for
- *   that country regardless of `defaultCountryCode`.
- * - Other inputs are returned as `+CC NNNN NNNN…` best-effort grouping.
+ * - A number that already carries a `+` country code formats for that country.
+ * - A bare national number formats for `options.country` when given, else for
+ *   the country implied by `defaultCountryCode` (default `+91`).
+ * - `includeCountryCode` controls international vs national format; defaults
+ *   to international whenever the country was detected rather than passed in
+ *   explicitly as `options.country`, and to national when it was.
+ * - Input libphonenumber-js can't parse into a valid number for the resolved
+ *   country falls back to a best-effort `+CC NNNN NNNN…` digit grouping.
  */
 export declare function formatPhone(input: string, defaultCountryCode?: string): string;
 export declare function formatPhone(input: string, options?: FormatPhoneOptions): string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webority-technologies/mobile-core",
-  "version": "0.0.3",
+  "version": "0.0.4",
   "description": "Platform layer for Webority React Native apps: HTTP clients, auth/token storage, config, logging, formatters, validators, network status, permissions, storage and version checks. No UI.",
   "keywords": [
     "react-native",