The command-line options that you need to use to start debugging have changed to -inspect and -inspect-brk. Debugging protocolsĪs you may know, in version 7+ Node.js changed its debugging protocol to the Chrome Debugging Protocol. Tip: another way to quickly run or debug a Node.js file is using the Run or Debug actions in the context menu of the JavaScript file. Explore the call stack and the variables in the debugging tool window, hover over the expressions in the editor to see their current state, step through the code, or put new breakpoints to help you debug further. Now if you do the actions that trigger the code where the breakpoint is, the app will pause on the breakpoint.

If you just want to run the app, click the green run icon next instead or press Ctrl-D / Shift + F10.

Now press Ctrl-D on macOS or Shift+F9 on Windows & Linux to debug the app (or click the green bug-like icon).

Now specify the path to the main file of the application that starts it.

To create a configuration, go to the Run menu and select Edit configurations… Click the + icon and select Node.js configuration type.We need to do two things: first, create a new Node.js run/debug configuration that will start the app, and then put a breakpoint. We’ll use a simple Express app as an example. And you can start debugging your app very quickly. In the debugging tool window, you can see the call stack and the variables in their current state, evaluate expressions in the editor, and step through the code – read more about that in the How to debug with WebStorm blog post. You can do many things that will help you explore the code and understand where the bug is.

You can put breakpoints right in your source code (no more debugger and console.log() statements!), which can be written in JavaScript or TypeScript. WebStorm makes it easier to debug Node.js apps.

Download jetbrains nodejs