Developer Experience: Use Chrome elements panel to interact with render tree #172
Labels
A-infrastructure
Area: Project infrastructure, build system, Ci, website etc.
enhancement
New feature or request
help wanted
Extra attention is needed
This is from @jchavarri and @jordwalke 's ideas on the Discord channel. A key value proposition of Electron is that it's really easy to debug - you get a built-in debugger with Electron! Right now, we don't have anything equivalent in the
revery
world.The idea Javier and Jordan had was that we could leverage the Chrome DevTools using either their integration API, or by creating pseudo-elements in the DOM and listen to mutation event
Potential Paths
Option 1: Integrate with the Chrome UI DevTools directly - Javier posted this link: https://www.chromium.org/developers/how-tos/inspecting-ash This documentation on the DevTools protocol looks helpful, too: https://chromedevtools.github.io/devtools-protocol/ This could open the door for inspecting Revery elements in the browser, as well as hooking up to other 'adapters' that speak the chrome debug protocol, like VSCode.
Option 2: Render pseudo-elements to the Chrome UI DevTools - Jordan showed how to create elements and then hook up mutation observers to essentially create a two-way sync.
These options aren't necessarily mutually exclusive; we could potentially use Option 1 for native and Option 2 for JSOO, for example!
Open Questions
revery
orreason-reactify
? The nice thing about it being inreason-reactify
is that any consumer of that library could also benefit from the developer tools!Chrome
instance with a special URL that accesses devtools + a host/port where therevery
debug adapter would be.The text was updated successfully, but these errors were encountered: