Webstorm nodejs debug code#

WebStorm’s debugger will use them to map the compiled code that is executed to the source code in the editor, and you will be able to put breakpoints in TypeScript code and step through it. There’s one extra thing you need for that – Source Maps. With WebStorm you can also debug code written in TypeScript (though you need to compile it to JavaScript first to run it with node). For any earlier versions it will use the old options and protocol. WebStorm will check the node version you’re using and if it’s 8+, it will use the new options and protocol. With WebStorm, you don’t have to worry about the protocols and options. 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.

Webstorm nodejs debug windows#

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.

Webstorm nodejs debug how to#

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. Running node apps in Docker from WebStorm.Attaching debugger to the running node process.The run profile works fine, but the same profile is not working for debug. But not sure what am I doing wrong with IDE. Even though it is up and running, I think.īy the way I know how to debug using node-inspector & browser. Now I can't open client UI application, which makes calls to this node.js/express REST service. It stops for the break points that I put in the beginning of the file, but after starting the server nothing happens. usr/bin/node -debug-brk=44917 -expose_debug_as=v8debug prompt in the console. I can run the application using the WebStorm IDE, but when I run the application, following is what I get in the console tab of debug panel. However lack of my understanding of node.js or for some other reason I cannot debug node.js application currently I am working on. I have used IntelliJ based IDEs in the past to configure to run and debug different programming languages. I recently joined the team which uses the node.js for the development.