Some configurations attach to the already started app, in this case, you need to specify the URL and port to attach to.
In the test configuration you can select between the name of a suite, test or a test file. To debug different types of apps and files, you need to use different types of run/debug configurations.ĭepending on the type, the information you need to provide in the configuration varies.įor example, in the Node.js configuration, you need to specify a file that needs to be run. Run/debug configuration is an entry point to, as the name suggests, running and debugging apps in WebStorm. Prepare for debugging: create a run/debug configuration Then we’ll put in some breakpoints, see what’s going on in the Debugger’s Variables view, step through the code, evaluate expressions and use the interactive console. We’ll start with creating a new run/debug configuration. To see how the debugger works in WebStorm, we’ll try to debug a simple Express Node.js application. If you want to edit the code or quickly navigate to the usages or definitions of methods while debugging, you don’t need to switch back to the editor.Īnd no matter what kind of code you debug, your experience with the debugger will be the same. One of the main benefits of using a debugger inside the IDE is that you put the breakpoints and step through your actual source code (even if you then compile it. In addition to that, you can also debug unit tests and build scripts. With WebStorm you can debug all kinds of applications written in JavaScript, TypeScript or Dart: Node.js, React Native and Electron apps and, of course, client-side apps written using different frameworks. The debugger is one of the most essential features of WebStorm.
0 kommentar(er)
