Why debug js in webstorm?

Question

JavaScript

Good afternoon, colleagues, such a question: the built-in debugging tools in Chrome / FF are much more convenient, more familiar, and that's it, than the built-in debug in php / webstorm, especially since files already collected by gulp / webpack and breakpoints in the source are transferred to the browser do not work (maybe the hands are crooked, I set it up for the first time). I have never used this functionality so far and, having configured it, I did not see any advantages of this approach, rather the opposite, since it lacks a lot of things. Explain - am I really losing any advantage by not using this IDE functionality or is it really useless and loses out to browsers?
I also request advice on debugging Javascript, features, maybe I'm missing something besides

Answer 1

Imagine such a case. You write a component, press ctrl+s, your watcher launches, the browser restarts, and nothing. The code doesn't work. You alttabat in the browser, press f12, console, see the error, go to source, find the file, set a breakpoint, understand where the error is and return to Webstorm.
So in WebStorm you are already in the context of your non-working component, so why not run the debugger directly on the component, for this you need to press one button and immediately see where you have a problem and fix it right on the spot. Sounds easier at least

Answer 2

You can set breaks and see the state in the same place where you write the code. I think that's all.
I also didn’t find any advantages for myself, it’s more convenient in the browser, you can use $0 and other browser chips with DOM, and if there are sursmaps, the browser also displays unpacked sources and puts breaks in them.

Answer 3

Debug NodeJS applications for example