A deprecated VS Code extension for debugging JavaScript in Chrome using the Chrome DevTools Protocol.
Debugger for Chrome was a Visual Studio Code extension that allowed developers to debug JavaScript applications running in the Google Chrome browser directly from the VS Code editor. It connected to Chrome using the Chrome DevTools Protocol, enabling features like breakpoints, step-through debugging, and variable inspection without leaving the code editor. This extension has been deprecated and its functionality is now included in VS Code's bundled JavaScript debugger.
Web developers using Visual Studio Code who need to debug JavaScript, TypeScript, or other web applications running in Chrome during development.
It provided a tightly integrated debugging experience within VS Code, eliminating context switching between the editor and browser developer tools. Developers could leverage VS Code's powerful debugging UI while interacting with Chrome's runtime, using source maps to debug original source files.
Debug your JavaScript code running in Google Chrome from VS Code.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enabled breakpoints, stepping, and variable inspection directly in VS Code, eliminating the need to switch between editor and browser, as shown in the demo and configuration examples.
Debugs original source files when source maps are enabled, with configurable overrides like sourceMapPathOverrides for frameworks like Webpack and Meteor.
Supported both launching a new Chrome instance and attaching to a running one, with detailed launch.json examples for different modes.
Provided browser console output within VS Code's Debug Console, creating a unified debugging environment as highlighted in the features list.
Officially deprecated and replaced by VS Code's bundled JavaScript debugger, meaning no further updates, bug fixes, or support.
Lacked support for key scenarios like debugging web workers and Chrome extensions, as admitted in the README's 'Unsupported scenarios' section.
Required precise setup of launch.json with webRoot and source mapping, leading to common issues like breakpoints not hitting, as detailed in troubleshooting sections.
Primarily designed for Chrome and similar targets; unofficial support for others like Electron came with caveats and no guarantees.