Debugging Your Angular Application in IntelliJ/WebStorm: A Step-by-Step Guide

On my first day at work, after learning that I would be working with Angular, I wanted to understand how Angular’s debugger worked to increase my somewhat limited knowledge. However, despite pressing the debug option in Angular CLI and placing breakpoints where necessary in my IDE, Webstorm, the debugger just wouldn’t work. In response to this situation, I made the decision, like any good engineer would, to postpone solving the problem. I began to console myself with the thought that I didn’t really need a debugger; I could find my errors without it. But deep down, somewhere inside me, I knew that this issue would come back to haunt me in the future, and eventually, I would have to solve it. A week passed, two weeks passed, and I continued to manage without needing the debugger. With each passing day, my confidence in the code I was writing and my debugging skills grew. I started to believe that I was unbeatable in software development. However, at the end of the Sprint, a problem arose that I couldn’t seem to solve, no matter what I did, no matter how many console.log statements I added. I just couldn’t figure out why the error was occurring. In that moment, I realized that the time had come to solve the debugger issue; and it was at the end of the Sprint, with a backlog of tasks to complete. Nevertheless, I tried to keep my composure, thinking that Webstorm was used by a lot of people, and surely someone else must have encountered this problem. I started searching the internet, but my anxiety grew as I found very few resources, and the ones I found weren’t working for me. After about 2.5 hours of scouring literature, I finally found the solution on a bug report page on <a href="https://youtrack.jetbrains.com/issue/WEB-59211/Cant-attach-debugger-to-Chrome-Dev-111-Invalid-handshake-response-getStatus-403-Forbidden" rel="noopener ugc nofollow" target="_blank">Youtrack</a>. Upon discovering the solution, I decided to share it as a guide for others who might face the same challenges, with the aim of helping them. I apologize for the long introduction, but I believe there are lessons to be drawn from this experience. I’ll leave it to you, dear readers, to determine what those lessons are. Another reason for the lengthy introduction is to help you appreciate the effort behind this seemingly short text. And yes, without further ado, let’s move on to the guide. <a href="https://medium.com/@erincayaz852/how-to-debug-an-angular-application-on-intellij-webstorm-dd60a5704b63">Visit Now</a>