This PR allows low-level access to V8's Inspector API, primarily to get call count/coverage data from it.
Theoretically it's possible to connect to V8's debugger this way. However I suppose this would cause problems, if you set a breakpoint in your JavaScript code, since that would block PHP code execution also. So I'd assume, in order to allow proper access to the debugger, further changes will be needed.
Also this only allows for programatic access to the inspector backend, i.e. it does not allow out-of-the-box connections from Chrome DevTools via websockets. However it should now be possible to implement a websocket server in PHP, that bridges messages with the V8Inspector instance (and then connect Chrome DevTools to that one).
A simple example regarding programatic access is shown in the README file
This PR allows low-level access to V8's Inspector API, primarily to get call count/coverage data from it.
Theoretically it's possible to connect to V8's debugger this way. However I suppose this would cause problems, if you set a breakpoint in your JavaScript code, since that would block PHP code execution also. So I'd assume, in order to allow proper access to the debugger, further changes will be needed.
Also this only allows for programatic access to the inspector backend, i.e. it does not allow out-of-the-box connections from Chrome DevTools via websockets. However it should now be possible to implement a websocket server in PHP, that bridges messages with the V8Inspector instance (and then connect Chrome DevTools to that one).
A simple example regarding programatic access is shown in the README file