On Sun, May 19, 2019 at 10:20 AM joe lewis <lewis.joe...@gmail.com> wrote: > > A bit more reading and I understood how dumb the question is. I'd like to > validate if my current understanding is correct. > > V8 is more than the shell binary that comes with the build. V8 provides > extensive C++ APIs to compile Javascript source code from other programs > (usually termed as embedding V8). > So, to enable chrome devtools as debugging front-end I have to write a > program (C++ wrapper or such) that communicates through web-sockets, > debugging-protocol messages back and forth from the front-end to v8. Or did I > get it completely twisted? > > If it did make sense, is there a project that has already implemented such > standalone program that statically links to V8 and exposes a remote-debugging > session? If nothing like that exists I'd like to pursue that direction and > publish a simple project that spins up a V8 instance and starts a chrome > remote-debugging session. > > Full-stack developer here, with almost no experience working with system > software. Please let me know if I got it all completely wrong. > > Thanks, > Joe
I haven't used it myself but several people recently reported in [0] that they had success with [1]. Your intuition about how DevTools integration works is on point, by the way. :-) [0] https://groups.google.com/forum/#!topic/v8-users/QUHnlvab13E [1] https://github.com/hsharsha/v8inspector -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-users/CAHQurc9vNzHTVG4SdxFdp43ahAzcqaX3r8O6rMPNrtWd%3D8g0eA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
