Bug: Browser stack trace cannot be determined when run on windows #323
Description
Describe the bug
The BaseLogger tries to examine the stack trace. While doing so, it parses the stack frames to get the filename, line number and character. When run on Windows, the file path contains a colon, which isn't handled properly by the parsing regex.
To Reproduce
Run a simple application, hosted on Windows and set a break point in BaseLogger.js in funtion parseBrowserStackLine.
Expected behavior
The file path (e. g. /@fs/C:/Git/MyApp/main.js) is parsed correctly.
OS incl. Version
WIndows 11 24H2
Tested in
TsLog 4.10.2