Description
I wanted to build an inspector for vdux to have some sort of visual indication of where your component lives instead of this giant div soup. Having a mid sized app becomes unmaintainable when inspecting.
Custom elements
One approach is to register a custom component for each vdux component. I know these custom elements are not supported except chrome and maybe firefox but we can still use them for debugging purposes. Then we don't need a custom dom inspector and we have the vdux tree right there.
This may be a start to at least have semantic components in the dom. No inspection of props and state though.
Custom debugger
Another approach would be to have a fully fledged debugger right in the devtools. I was thinking of something similar to vue-devtools. The benefit over this to custom elements that we can add support for also inspecting props and possibly local state.
Core extensions
We definitely need some kind of core support for naming components. Right now there is no way to retrieve a component's name
Do you have any opinions / suggestions on that? I would like to hack something together!