Source map browsers do not load when debugging in Chrome

I am developing an Angular application. While trying to debug my directory link, I ran into problems with Chrome regarding the source maps.

When you first load the page (caused by Gulp and BrowserSync), everything is just nice and dandy: I ​​can see both the file being watched and files with one source from the map. There is an error in the console, so I click on the call trace to examine it, and the correct line of code will be shown inside the source file - as expected.

The problem starts with setting a breakpoint in my code and restarting the browser for debugging. Execution stops at the breakpoint - ok -, but apparently the source file has not yet been loaded. Instead, where the source file used to be, the text of the friendly green letters tells me:

Wait a bit. The compiled script does not appear when loading the source map!

It is right. I see on the sources tab that it really is not loaded, but nothing else happens (presumably due to a breakpoint).

I have never had this behavior before. I don’t think this is due to my original Browserify maps, rather I suspect this is a problem with Chrome.

In Firefox, everything works as it should. But I prefer Chrome for Firefox, so ...

Have any of you ever come across this problem or had any idea what might cause it?

The version of Chrome I'm working on is using version 41.0.2272.118 (current on asking this question).

+6
source share

Source: https://habr.com/ru/post/986442/


All Articles