You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understand correctly, simply running the command npm install --save tldjs --tldjs-update-rules should update the list of tlds globally.
I'm working on a tool that uses tld.js to check validity of email addresses, we have had several customers writing in being unable to sign up with their domains.
In my local dev environment, I saw that tldExists was returning false for a specific domain. After running the above command, the same argument began to return true, so I imagined the list of tlds had been updated successfully.
However the value continues to return false in staging and production. Am I missing something here?
Thanks!
The text was updated successfully, but these errors were encountered:
I believe you might need to run this command after installing your dependencies in your staging and production environment as well (the command might need to be executed explicitly, maybe as a postinstall hook in your project?).
If I understand correctly, simply running the command
npm install --save tldjs --tldjs-update-rules
should update the list of tlds globally.I'm working on a tool that uses tld.js to check validity of email addresses, we have had several customers writing in being unable to sign up with their domains.
In my local dev environment, I saw that
tldExists
was returning false for a specific domain. After running the above command, the same argument began to return true, so I imagined the list of tlds had been updated successfully.However the value continues to return false in staging and production. Am I missing something here?
Thanks!
The text was updated successfully, but these errors were encountered: