Unexpected validation response for `<name>:<port>` URLs

[octavian-mto]

Describe the bug
isURL returns false for urls like some-hostname:9000 after 13.15.20 version bump, 13.15.15 works as expected returning true

Examples

validator.isURL("my-3272-service:9000", { require_tld: false, require_valid_protocol: false });  // returns false in 13.15.20 instead of true

Reproductions
If applicable, provide a reproduction on platforms like runkit

Additional context
Validator.js version: 13.15.20
Node.js version: 22.14.0
OS platform: linux

[WikiRik]

Thanks for reporting this issue! I was already expecting that we would introduce regressions, our test suite is definitely not covering everything.

If people want to take this up, this is at least something that should pass;

  it('should validate URLs that do not have a TLD', () => {
    test({
      validator: 'isURL',
      args: [{
        require_tld: false,
      }],
      valid: [
        'http://foobar.com/',
        'http://foobar/',
        'http://localhost/',
        'foobar/',
        'foobar',
// The valid URLs below should be added to the test
        'localhost',
        'localhost:3000',
        'service-name:8080',
      ],
      invalid: [],
    });
  });

[WikiRik]

13.15.22 is released which includes a fix for this