WebStorm 2020.2 Beta: Start Debugging from Run and Terminal Tool Windows
WebStorm 2020.2 Beta is now available! To catch up on what has already been implemented in v2020.2, check out our previous EAP blog posts.
The Toolbox App is the easiest way to get the EAP builds and keep your stable WebStorm version and any EAP versions up to date. Or you can download the EAP builds from our website. You can also choose to be notified right from the IDE when a new EAP build is available: go to Preferences/Settings | Appearance & Behavior | System Settings | Updates and select Automatically check updates for Early Access Program.
Important! WebStorm EAP builds are not fully tested and might be unstable.
Here are some of the highlights of WebStorm 2020.2 Beta (build 202.6250.10). For the full list of issues fixed in this update, see the release notes.
Start debugging from the Run and Terminal tool windows
Starting with this build, the IDE will offer a quick way to start a debug session from the Run and Terminal tool windows.
Let’s say you want to run a script like
For ws:// links, the IDE will start a Node.js debug session using the Attach to Node.js configuration. To try it out, run the node or nodemon command in debug mode using the –inspect or –inspect-brk flags and repeat the same steps as above.
Those are the biggest highlights. This build also comes with some smaller, but still important changes, such as:
- If you’re debugging code containing
arr[i], WebStorm will show a slightly more helpful inline preview for it in the editor.
- The way smart command handling works has changed. For macOS, you’ll now need to use Cmd+Enter to run the highlighted action using the relevant IDE feature instead of the terminal. For commands like
npm start, the IDE will now start a debug session only if you use a dedicated shortcut for it – Cmd/Ctrl+Shift+Enter.
Please report any issues you encounter to our issue tracker. And stay tuned for next week’s update!
The WebStorm team