"Blackboxing" in Chrome vs. "Do Not Step Into Library Scripts" in IntelliJ | Debugging Issue
I'm developing for an Angular project. I'm new to IntelliJ and Angular and I would like to use the debug functionality in IDEA. My hope is to only debug "my code". In other words, I don't need to see anything that isn't in /src. I've learned this is possible in IDEA by enabling the option "Do not step into library scripts". In Chrome, it's done using "blackboxing".
Well, whenever I try to step within IDEA and there's some sort of call to a library script, IDEAs debug window will freeze and Chrome's dev tools will start walking through the corresponding library files line by line. It will sit there and execute one line about every second without any interaction from me. I'm just watching it highlight the lines it's executing. I then have to wait until it gets back to a "my code" file before I can do any stepping in IDEA. Sometimes it takes a few seconds and sometimes a few minutes. If I use chrome's debug buttons, then I have total control over what is stepped into, out of, and over, but I still run into files that I don't care to see.
If I disable "Do not step into library scripts", that fixes the issue with chrome executing things without my input. However, now I can't avoid stepping in to files or stepping out to files that are not a subset of "my code".
The other thing I tried was to mess with blackboxing in Chrome. I reenabled "do not step into library scripts" in IDEA and then in Chrome, I blackboxed a specific file that was referenced frequently. However, when I started debugging in IDEA, the same wait-for-chrome-to-catch-up issue happens AND chrome still enters the file that I blackboxed.
I don't know if IDEA and chrome are just miscommunicating on what files to debug through or what? But I'm just really hoping I can avoid debugging files I don't need to.
Let me know if you need more information. Any help is appreciated! I'm very new to all of this so please forgive and correct any misunderstandings I have about how this works.
Please sign in to leave a comment.
Someone is having the same issue but with React in Webstorm. Their description fits my problem exactly. https://stackoverflow.com/questions/57345387/how-can-i-debug-react-apps-in-webstorm
Please follow https://youtrack.jetbrains.com/issue/WEB-41714 to be notified on updates.
Oksana Chumak Elena Pogorelova I noticed that issue pertains to Webstorm. Should I assume a fix there would also fix IDEA or does it need to be a separate issue? (I'm new here)
The host project for JavaScript Debugger is WebStorm, WebStorm provides the corresponding functionality to other IDEs. So no separate tickets are required, WebStorm fixes will be available in other IDEs.
Thank you! Good to know.