Improve error message when parsing fails

[simhnna]

I got error messages like TypeError: Missing parameter name at 3: https://git.new/pathToRegexpError and I was wondering how that weird url made it's way into my code

Two suggestions:

1. It doeesn't look like lexer() gets the whole error, so maybe it would be good to wrap those errors in parse() and include the whole string?
2. Make it clear that the url is documentation. Something like For more information about regexp paths check https://...
3. I personally would prefer a link that clearly shows it's going to github instead of a link shortener, but that's just my opinion

If you're ok with me changing 1 and 2, I'm happy to prepare a pull request

[blakeembrey]

1. I'm not sure I understand, can you elaborate on what "the whole string"?
2. Sounds good, I'm open to a PR that changes it to something like ...; visit <link> for more information.
3. Prefer to avoid changing for now, it's there to ensure the error docs can move or update in the future without breaking old versions of the library.

[abs-lme]

For 1, I guess the problem is that the error message gives no indication on where the error occurred. I have the same error stating something about 'missing parameter name at 2' without any details. So I have to check all my routes for potential errors. Dumping the input path will already help with handling this error.

[simhnna]

I'm sorry I completely forgot about that. I created two merge requests that address points 1 and 2

[SlothScript]

I have created a simple version of this that shows you the problematic url. pull request #358