You can add a new problem matcher that matches pretty output:

{
                    "regexp": "^([^\\s].*):(\\d+:\\d+) - (error|warning|info)\\s+(TS\\d+)\\s*:\\s*(.*)$",
                    "file": 1,
                    "location": 2,
                    "severity": 3,
                    "code": 4,
                    "message": 5
}

Looks like the tsc problem matcher does not handle --pretty output for locations..

So we can either change it on our side and have --pretty emit the same file name/line number similar to the non-pretty mode, or we can add a new problem matcher regex or modify the tsc problem matcher.

@dbaeumer what would be your preference?

I fixed it on our end. Having two problem matchers is not nice for the users.

@mhegazy one thing: the fix now assumes that a message only contains line,column information and never line,column,endline,endcolumn which was possible with the old matcher. But to my knowledge TS always emitted line,column only. Right?

@mjbvz please review #48744 and merge if you think the fix is fine.