Update all-countries.js [main & legacy branches]

[AlexeyZelenko]

Hi,
Will we have an updated list in vue-tel-input@legacy?
+61 461 294 482
mobile number is not being accepted. It says "Phone number is wrong for selected country."

Displayed here correctly:
https://vue-tel-input.iamstevendao.com/

Thank you.

[iamstevendao]

@AlexeyZelenko can you send the props you are using?

[AlexeyZelenko]

<tel-field id="contact-phone"
ref="telField"
v-model="phone"
:default-country="defaultCountry"
@country-changed="phoneCountryChange"
:auto-default-country="true"
:input-options="phoneInputOptions"
@input="onInput"
@Validate="validatePhone"
class="checkout-contact--input-phone" />

[AlexeyZelenko]

"vue-tel-input": "^5.15.0"

[AlexeyZelenko]

@iamstevendao
Your dependencies are outdated, could you update it?
"libphonenumber-js": "^1.10.12"

Current version
1.10.59

Applies to Vue3 now
"libphonenumber-js": "^1.10.51"

Please update the version vue-tel-input@legacy

[AndrewFeeney]

I am also experiencing this issue with vue-tel-input 5.15.0 and an Australian phone number with the pattern +61 461 *** ***. I've tested by building from source with the latest version of libphonenumber-js and it works. Because libphonenumber-js is being bundled within the dist module, whatever version is current when the package is built for release is the one that gets shipped, even though the dependency constraint ^1.10.12 would match the latest version. Unless I'm mistaken you'll need to run npm update libphonenumber-js and rebuild and release a patch release this every time that package is released to include the updated version of the dependency. Alternatively, libphonenumber-js could be made a peer dependency, and users of the package can rebuild their own projects pulling in the latest libphonenumber-js as needed when it is released.

[rphq-nathanz]

I noticed something strange in allCountries.js
The entry for Guernsey has 4 elements

[fajardokarl]

Hi, any solution for this issue? I'm also having an issue with AU number format (+61 461 *** ***). Similar case with @AndrewFeeney