url-regex

url-regex copied to clipboard

urls with `@` followed by `.` and number are parsed incorrectly

1

```js console.log("https://test.com/@foo.bar1baz".match(require('url-regex')({strict:true})))` ``` ``` [ 'https://test.com/@foo.bar' ] ```

DetachHead

Hi there! I am running into an edge case in our application where if a user inputs an incorrect email address, for example, `m.me@ff`, the library will return `m.me` as...

Dodie324

Increasing tlds list accuratness by `(?![a-z])`

5

Thanks to that little piece of regexp code, strings like: I'am `Damian.Ga`thering is my favorite skill won't be matched

Kamil93

Update `tlds`

1

// @sindresorhus

Richienb

Don't allow ' in path

5

failing test case: `background: url('http://example.com/pic.jpg');` resulted in `http://example.com/pic.jpg'` fixed #54

alexpusch

urls that are enclosed with ' instead of " are not matched correctly

2

This happens because of the path regex that should be changed to const path = '(?:[/?#][^\\s"\']*)?';

regevbr

Update path regex to not accept closing parens

18

This fixes a few cases, one of which is documented in #34: * css url's of the format `background-image:url(http://example.com/img.jpg);` * markdown url's such as `look at [my image](http://example.com/img.jpg) blah blah`

skyebook

Add `local` option.

2

@SamVerschueren can, you, please, check this one?

samotlark

Add option to disable matching urls with http basic authentication

1

Fixes #51 by adding an option to disable the HTTP Basic Authentication regex that matches on emails. It's worth noting that without the `exact` option the regex will match: `[email protected]`...

sseppola

Pass in own list of TLDs

1

Context at #65 Didn't add typings or readme yet, want to see if this kind of API is something you'd be open to. Adds a new entry point to preserve...

osdiab