I hope this helps someone else out because it drove me nuts for the longest time. It can be downloaded from the Chrome Extension store here. It was my understanding that this was no longer needed in the newer versions of WebStorm but it appears that to debug my Angular application it is still required. So they key was the JetBrains IDE support Chrome Extension. At that point the WebStorm IDE opened a second DEBUG window named 'localhost:4200'. Once installed, I right clicked on the extension and chose 'Inspect in WebStorm' option. Then I installed the JetBrains IDE Support Chrome Extension. The any breakpoints I had set were hit whenever I triggered them. At this point my application would run normally but no breakpoints would be hit. At that point the WebStorm IDE opened a second DEBUG window named "localhost:4200". Once installed, I right clicked on the extension and chose "Inspect in WebStorm" option. At this point my application would run normally but no breakpoints would be hit.From here I could launch my Angular application and webpack would compile everything.You can ignore the Script parameter in the screenshot as this is simply an alias (located in package.json) pointing to a JSON file that contains proxies for external API endpoints (DEV, Production, Stage, etc) I setup a debug configuration using the WebStorm "npm" template (screen capture below).I finally got it to work after much trial and error.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |