You'll then create a launch-configuration file which we explain in detail in our README right here. When the extension list appears, type 'chrome' to filter the list and install the Debugger for Chrome extension. To get started, open the Extensions view ( ⇧⌘X (Windows, Linux Ctrl+Shift+X)). This is slightly annoying, and we hope this issue will be fixed sometime soon. This means if you open up DevTools inside Chrome, the connection to VS Code will get terminated by Chrome. Supporting source maps also enables debugging of TypeScript straight from VS Code.įor now, Chrome needs to be started with remote debugging enabled, and only supports one concurrent connection. This works because our debugger understands JavaScript Source Maps, which we’ll use to enable developers to debug straight from their original source, and not the transpiled result that the browser sees. In the above example, we are showing an AngularJS app bundled and minified via Browserify being debugged from VS Code.
This means developers now can set breakpoints directly in their source code, set up variables to watch and see the full call stack when debugging - all without leaving the editor. Our debugger works by connecting to Chrome over its Chrome Debugger protocol, where we map files loaded in the browser to the files open in Visual Studio Code.
Our Chrome Debugger allows front-end developers to debug their client-side JavaScript code running inside Google Chrome directly from Visual Studio Code.
NET and Node.js debugging, and today we are taking the next step by introducing our Chrome Debugger for Visual Studio Code. Since the first release of Visual Studio Code, one of our focuses has been to simplify the daily workflow for developers by enabling them to debug their code directly from the editor. Node.js Development with Visual Studio Code and Azureįebruby Andy Sterland and Kenneth Auchenberg.Moving from Local to Remote Development.
0 kommentar(er)
