Angular4 Update from CLI 1.0.6 to 1.1.2 somehow breaks the WebStrom debugger

Hi

I spent rather a long time narrowing down the problem. Looks as the upgrade of an Angular project does break the debugging capabilities

Works under @angular/cli1.0.6 using angular @angular/core@4.1.3

Fails to debug under @angular/cli1.1.2 using angular @angular/core@4.2.3

I downloaded as well WebStorm-172.2953.12.exe. This on showed a crash in the WebPack loading (and I used the feedback to report).

Illegal char <:> at index 40: C:/js_prj/AngularTraining/Test2\/webpack:/C:/js_prj/AngularTraining/Test2/~/@angular/core/@angular/core.es5.js

I hope my summary makes sense. For the moment I switched back to the older version of angular.

regards Günther

 

 

 

 

 

 

4 comments
Comment actions Permalink

angular-cli has changed the way sourcemaps are generated. Please see https://youtrack.jetbrains.com/issue/WEB-27381#comment=27-2249066 for a workaround

0
Comment actions Permalink

thank you for the very fast answer. I tried the workaround but looks as "ng eject" + "npm start" does somehow not work as expect (raises some internal warnings). But I assume this is a problem based on all my installs / uninstalls.

Most important that JetBrain is now aware of the problem and I assume that it will be solved with the next major release of WebStorm (and hopefully Angular gets as well stable during this time).

best regards Günther

 

 

0
Comment actions Permalink

I'd rather consider this a problem with angular-cli + SourceMapDevToolPlugin webpack plugin: absolute paths in sourcemaps not only break WebStorm debugger, but make the application not portable - as soon as you copy your application to a different location, sourcemaps will immediately stop working

0
Comment actions Permalink

OK - agreed. Then we should keep this issue in mind and crosscheck with the next versions of angular-cli.Hopefully it's solved by such an angular upgrade.

0

Please sign in to leave a comment.