Provide experimental access to V8's Inspector API #445
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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