- By David Ramel
- July 15, 2020
Working with Node.js and Chrome, the debugger that has been in the works for months is now the default option in the June 2020 update, or VS Code 1.47.
Features and functionality for the debugger as listed on its GitHub site include:
- Debug child process and workers
- Debug Node.js processes in the terminal
- Profiling support
- Easy npm script debugging
- Automatic browser debugging
- Instrumentation breakpoints
- Better autocompletion in debug console
- Return value interception
- Top-Level await
- Pretty-print minified sources
- Support for Microsoft Edge and WebView2
- Better sourcemap and breakpoint behavior
- Copy values in call stack view
Also, this week's post announcing VS Code 1.47 lists:
- Single file debugging: This provides functionality found in other debug extensions, with new icons in the title area indicating debugging can be kicked off with a button click.
- Less cluttered CALL STACK view: This is achieved by hiding debug session nodes that exist for technical reasons, but do not provide much value to users.
- New command alias Set Next Statement for Jump to Cursor: To make the command Jump to Cursor more discoverable for users coming from Visual Studio, the dev team added the command alias Set Next Statement.
- Breakpoint Path on Hover: In the BREAKPOINTS view, hovering over a source breakpoint shows its absolute path.
All of the above and more is presented in greater detail in the announcement post.
David Ramel is an editor and writer for Converge360.