Bump to support intl-tel-input < Number.MAX_SAFE_INTEGER

[tlebreton]

Hi :)

This pr allow us to use intl-tel-input 20 Changelog

I needed to update test unit because of this :

Remove defaultToFirstCountry option as that behaviour was jackocnr/intl-tel-input#1525 (comment) and so is not recommended (you can always use initialCountry to set the initial country if you wish to)

I decide to add initialCountry: "ch" because it solve test but don't know if it's correct or not.

Another thinks that changes is the way validNumber works :

By default, calling isValidNumber will now default to mobile-only mode (it will only return true for valid mobile numbers), which means it will be jackocnr/intl-tel-input#1535 - if you don't want this, you can pass false as an argument e.g. isValidNumber(false)

It can be solved with another options 'isMobileVerification' with default to true(like intl-tel-input)

What is your opinion on this subject ?

[mpalourdio]

Wow, another upstream breaking update, so cool (no).

I suggest we wait for one week or two. The last version (19) has had lots of releases in its short life days. And from what I see, this one has already 4 updates since yersterday :D

[tlebreton]

Yeah i fully understand you :D

Please leaves it open and in the begin of april i will be back to you.

[jackocnr]

uh oh, you guys are really going to hate me now 😂

[mpalourdio]

@jackocnr @tlebreton we shoud move to "intl-tel-input":">20.0.0" in package.json once and for all, then watch the world burn, WDYT ? 🥲

[mpalourdio]

I have update the PR title accordingly 😆

[tlebreton]

I will take the time by the end of the week to update the pr according to change made by @jackocnr