react-error-overlay fails to parse typescript errors #7082

Is this a bug report?

yes

Which terms did you search for in User Guide?

react-error-overlay

Environment

Steps to Reproduce

In a create-react-app typescript project:

1. Start the development server
2. Make a typescript error in any file (let a: string = 0 for example).
3. The error overlay displays the error, however clicking on the exception does not navigate to the file in the text editor as with other webpack errors.

Expected Behavior

Clicking on the error overlay navigates to the file in a text editor.

Actual Behavior

The error overlay isn't clickable.

Details

React-error-overlay tries parsing the exception by looking for a filepath in the error message. This is handled in parseCompileError.js, where the filepath regex matches only relative paths:

const filePathRegex = /^\.(\/[^/\n ]+)+\.[^/\n ]+$/;

whereas typescript errors use absolute paths. As discussed in #6502 (comment) making the paths relative has some drawbacks so it would be best to keep them absolute.
Also TS error locations are specified like (line,colon) so we would need to add that format to the lineNumberRegexes array.

I can submit a PR for this if that's okay.