You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to implement and expose suitable send and receive functions so that a user of the non-ND version of Espresso could access Inspector Protocol for debugging purposes.
My ideal would obviously be to be able to use ChromeDevTools in the same way that ND users can as seen in #39 however I'd be happy to start with very basic access to allow me to build a basic debugger.
The documentation at https://v8.dev/docs/inspector seems to imply that this should be fairly straight-forwards, however I haven't written any C++ for many years, so have no idea how to go about this myself.
I also believe that there's a good chance that if we could set up a suitable Inspector Protocol redirector, it could be integrated with Visual Studio's javascript/NodeJs debugging facility without too much work. Ref https://code.visualstudio.com/docs/nodejs/nodejs-debugging and I'd be happy to have a try at that.
The text was updated successfully, but these errors were encountered:
Would it be possible to implement and expose suitable send and receive functions so that a user of the non-ND version of Espresso could access Inspector Protocol for debugging purposes.
My ideal would obviously be to be able to use ChromeDevTools in the same way that ND users can as seen in #39 however I'd be happy to start with very basic access to allow me to build a basic debugger.
The documentation at https://v8.dev/docs/inspector seems to imply that this should be fairly straight-forwards, however I haven't written any C++ for many years, so have no idea how to go about this myself.
I also believe that there's a good chance that if we could set up a suitable Inspector Protocol redirector, it could be integrated with Visual Studio's javascript/NodeJs debugging facility without too much work. Ref https://code.visualstudio.com/docs/nodejs/nodejs-debugging and I'd be happy to have a try at that.
The text was updated successfully, but these errors were encountered: