Repository navigation
Legacy JSON debug API removed as of V8 5.8 #9789
Description
Activity
/cc @nodejs/diagnostics @nodejs/v8.
Oh shoot was this the original issue, whoops I guess it was around the code-and-learn and no-one saw it. :(
- changed the title
[-]Legacy JSON debug API removed as of V8 5.7[/-][+]Legacy JSON debug API removed as of V8 ~~5.7~~ 5.8[/+]on Jan 23, 2017 - changed the title
[-]Legacy JSON debug API removed as of V8 ~~5.7~~ 5.8[/-][+]Legacy JSON debug API removed as of V8 5.8[/+]on Jan 23, 2017 The functionality of the legacy JSON debug API has been removed for V8 5.8: https://chromium.googlesource.com/v8/v8/+/876da98a5182a03f631f9ab4469bd6838225cb16
The API is still there so that Node.js still compiles. But these are only dummy functions.
wow sorry for cluttering this issue up with all my interim test fixes :). also accidentally closed it with a "Fixes" comment, so reopened.
- added 2 commits that reference this issue
on Feb 25, 2017 I wanted ask if a
debug2inspectbridge was proposed (a proxy that translates thedebugprotocol intoinspect) ?
Was it discussed how feasible that is?
Re: regression: 3rd party debuggers are incompatible with node8 nighliesThis seems close-able at this time. If I'm mistaken, by all means, re-open or comment.
- added a commit that references this issue
on Jul 27, 2026
This has been announced several times in the past two years [0][1]. Now that v8-inspector has taken over as a viable alternative, the old and unmaintained JSON debug API is now finally being removed from V8 [2]. I suggest migrating over to the inspector protocol if your tool talks to node/v8 via the legacy JSON debug API.
[0] https://docs.google.com/document/d/1M8DdgDldglYjQJ1mu0yBzwgR6lCX-ZKS_hxAJiCLT34/edit
[1] https://github.com/v8/v8/wiki/Debugging-Protocol
[2] https://chromium.googlesource.com/v8/v8/+/81a64aa5488602e4643f1ecc3beeddb8828a853c