Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Commit 5b97c7f

Browse files
committed
Add Gitter badge
1 parent 889e48e commit 5b97c7f

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,6 @@
11
# VS Code Node Debug 2 (Experimental)
2+
[![Gitter](https://badges.gitter.im/Join Chat.svg)](https://gitter.im/microsoft/vscode)
3+
24
This repository contains an experimental debug extension for [node.js](https://nodejs.org) that ships with [VS Code](https://code.visualstudio.com) and uses the [Chrome Debugging Protocol](https://chromedevtools.github.io/debugger-protocol-viewer/v8/), which Node now exposes via the `--inspect` flag, only in Node versions 6.3+. It's built on the [vscode-chrome-debug-core](https://github.com/Microsoft/vscode-chrome-debug-core) library.
35

46
This extension will eventually have feature-parity with vscode-node-debug, but isn't there yet. An overview is recorded [here](https://github.com/Microsoft/vscode-node-debug/issues/7) and you can see issues in the [vscode-node-debug2](https://github.com/Microsoft/vscode-node-debug2/issues) repo and the [vscode-chrome-debug-core](https://github.com/microsoft/vscode-chrome-debug-core/issues) repo. For the most part, you should be able to set `"type": "node2"` in your existing Node launch config and have things work the same, as long as it's running in Node v6.3+.

0 commit comments

Comments
 (0)