Repository navigation
proposal: programmatically expose the V8 inspector URL #11496
Description
- Version: 7.6.0 and later
- Platform: all
- Subsystem: diagnostics
This is a feature request to add a method to the v8 module that exposes the V8 inspector URL if the process has been started with --inspect. The motivation for this feature is to conveniently add links or buttons to a website that the developer can click to open the V8 inspector.
This is a hypothetical API:
$ node --inspect=dev.example.com:1337
> require('v8').getInspectorUri()
chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=dev.example.com:1337/8fe96e86-fa03-4a24-b21d-2ce3725e479e
$ node
> require('v8').getInspectorUri()
null
Activity
bnoordhuis commentedon Feb 22, 2017
Should be easy enough to do but let's see what @nodejs/v8-inspector thinks.
Fishrock123 commentedon Feb 22, 2017
Sounds like a good idea to me. I think it should probably not be on the V8 module though?
eugeneo commentedon Feb 22, 2017
We have plans of introducing bindings for inspector API (it is currently blocked on inspector becoming the default debug API, e.g. by installing the debug signal handler). I believe we could expose this url as a part of that API. API details are still TBD (e.g. I did not even open a pull request)...
joshgav commentedon Feb 22, 2017
FWIW you can get the URI and other metadata like the UUID from the JSON returned from
http://localhost:9229/json/list(orhttp://localhost:9229/json) too. See #11207 for an example of that output.@ofrobots @cristiancavalli @eugeneo are working on providing a JS API to Inspector in general, perhaps access to the
listJSON object could be part of that API and cover this request too./cc @nodejs/diagnostics
jasnell commentedon Feb 22, 2017
This seems like a good idea. Perhaps even one step further ... an API that simply returns the same data as the
/json/listendpoint.As for where it should live, perhaps when running with
--inspect, this can be exposed viaprocess.inspectInfo()API. When running without--inspect, it would simply returnundefinedeugeneo commentedon Feb 22, 2017
rumkin commentedon Mar 5, 2017
I think this URI should be also predictable and partially configurable from command line. As I mentioned in #11701 I'm working with remote debug and automated tools doesn't allow to extract this URI from node output.
Trott commentedon Jul 30, 2017
Is this in progress? Stalled? Blocked? Help wanted? I guess /cc @eugeneo but really anyone that knows?
TimothyGu commentedon Jul 30, 2017
The requested feature is now provided in inspector.url(), so closing.
inspector: allow --inspect=host:port from js