I've followed numerous documents/tutorials to no avail. It looks like someone in the past asked a very similar question but it was not answered exactly but that was two years ago.
2
-
Afaik, you can't - they're client-side.JanS– JanS2018-01-24 17:13:13 +00:00Commented Jan 24, 2018 at 17:13
-
blog.jetbrains.com/webstorm/2017/01/debugging-angular-apps ?LazyOne– LazyOne2018-01-24 21:10:18 +00:00Commented Jan 24, 2018 at 21:10
Add a comment
|
1 Answer
AngularJS application running/debugging doesn't differ from any other javascript client-side application running/debugging: you need a JavaScript Debug run configuration for this. The way your Angular application is served (via a custom node.js server, Gulp, WebStorm built-in web server or any other web server) matters nothing - you just have to specify your application URL (the one you use to access it in browser) as URL in your Run configuration. see https://www.jetbrains.com/help/webstorm/debugging-javascript-in-chrome.html, Debugging an application running on an external web server
2 Comments
musicformellons
Tried this and seems to me you can then just debug the compiled JS, so "after gulp". Would be nice to have breakpoints in pre-compiled code and have these working. Or am I doing something wrong?
lena
must be a problem with sourcemaps - they are either missing or not accurate, so the sources can't be mapped to the compiled code being run. make sure to that
'gulp-sourcemaps' package is used and configured properly