Closed issue-submission closed 9 months ago
It seems that a few suggestions could be found here. Not sure how much would that affect the matching speed.
I suppose that this package is not trying to validate if the URL address in that much detail.
validator.isURL
or another URL validator should be used on matches - however we'd welcome a PR to fix this and then would do a major semver bump on release to npm/GitHub
Hi,
It seems that the regular expression considers as valid URLs containing a port that is not valid. For example: http://localhost:99999 or https://www.iana.org:65536.