Nikolay

Hi. No one has ever reported something like that. Supposedly, it could be something with your code. I dunno. I won't be looking into this due to being busy. Also...

Also, perhaps you're importing `parsePhoneNumber` from an incorrect path. Instead, do this: ```js import parsePhoneNumber from 'libphonenumber-js/max' ```

Getting same error. The package is broken and unusable. Author doesn't know how to properly publish npm packages. Workaround: `yarn add [email protected]`. Do not update the package version, or your...

@theKashey > for now I am going to republish `2.11.3` as `2.12.1` I'd suggest doing that. * If there're no production apps or packages that already use `2.12.0` then there's...

@likegs9 The bug seems to be fixed. After installing the new verison, there's no error.

Seems to be working (in our projects).

@Jack-Barry I can see that the error is reproducible in the sandbox you've provided but it also contains a non-latest version of `react-phone-number-input` as a dependency. But when updating `react-phone-number-input`...

@Jack-Barry I did replicate the issue locally on my machine using the code you've posted in that sandbox. Your gess about the line of code where the bug is manifested...

Ok. Since s sandbox doesn’t seem to be working with the latest version, simply post your code and steps to reproduce. On Fri, 5 May 2023 at 00:59, Jack Barry...

> Found a site that'll allow it to work on latest: I can see that the demo is working. What issue're you having with its operation?