Reputation: 2554
Without any change in configuration, I can no longer debug Angular TS files in Chrome, either by setting manual breakpoints in Dev Tools or by debugger;
statements. Facts of the situation:
Development
, not Production
tsconfig
has "sourceMap": true
debugger;
lines aren't being hit at allWhat's strange, however, is that when I open the app in Safari, the debugger;
breakpoints are hit, and I can set manual breakpoints in TS files just fine. So that leads me to believe that this is a Chrome issue and not an Angular configuration issue.
Specs => Chrome: Version 75.0.3770.142 (up-to-date as of this post), Angular: 6.1.2 (Project requirement, so this can't be updated)
Upvotes: 2
Views: 7221
Reputation: 2554
After writing this all up, I realized the issue was caused by having another Angular project directory loaded into Dev Tools. The automatic mapping was looking at the src
directory of this other project rather than the current project I was working on.
.scss
instead of .css
, so no match was found thereIf anyone knows of a way to avoid this problem moving forward, please let me know! I work on multiple projects simultaneously very frequently, so it would be nice to not have to remove each project when switching to a new one.
Upvotes: 3