ntbang0901 fdf29989ec feat(debugger): debug JavaScript that runs in the browser (#3294) ...

Code running in a browser could not be debugged: js-debug was only started for Node.js and launch.json entries of type chrome / msedge were skipped on import. A JavaScript Debug run configuration (URL, Chrome or Edge, web root) now opens the page with js-debug attached, so breakpoints in the page's sources are hit through source maps with the usual stepping, variables, evaluate and console. Each project gets its own browser profile under the IDE's local data, a project has one debugged browser of a kind (starting again reuses it), launch.json chrome / msedge launches import as this configuration, child sessions named about:blank take their parent's name, and Vue, Svelte, Astro and HTML files take breakpoints. Not yet available in remote projects.

Co-authored-by: ntbang0901 <121003585+ntbang0901@users.noreply.github.com>

2026-11-14 13:49:21 +08:00

..

examples

Initial open-source release

2026-10-22 18:55:10 +08:00

src

feat(debugger): debug JavaScript that runs in the browser (#3294)

2026-11-14 13:49:21 +08:00

tests

feat(debugger): debug JavaScript that runs in the browser (#3294)

2026-11-14 13:49:21 +08:00

Cargo.toml

fix(go): run file-scoped tests in their real package (#1987)

2026-11-08 00:14:21 +08:00