Description
I just spent pretty much the whole day trying to get vscode debugger to stop on breakpoints set in typescript files.
The issue ended up being that one of the files in my project was importing a resource from a file using wrong file casing (and it just so happened to be that this file was the one I was trying to set breakpoints in) ...
import { foo } from "../bar/Awesomebaz"
With the target file actually named 'AwesomeBaz.ts'.
No warnings or execution problems occurred from this mistake ... Everything seemed to work except my debugging experience was myseriously broken in a very hard to understand way. It took a long time to discover the forceConsistentNaming compiler flag and get the idea to try turning it on which led immediately to the correct fix.
I think having this flag off is a bad default -- I would like to suggest turning it on by default instead. Or at least turn it on when strict: true ...