Attach the debugger in the extension content script about solid-devtools HOT 3 CLOSED

Ok, so there is a different problem that I didn't think of—loading the debugger by injecting a script tag effectively loads a second solid runtime on the page.

This may be a problem, or maybe it won't—it depends if the debugger at any point will need to interact with the application's solid runtime. For example:

• when users want to register their own plugin. Or interact in any way with it.
• when the debugger would need to use some of solid's primitives to get information out of the application graph.

It would be great to be able to just install the extension and that's it, but I think we're stuck with an npm library approach. It's not that bad though.
In the future, we might go in a different direction, that provided a similar experience—there are couple of core solid members that would be happy to add the debugger to solid-start or even solid itself.

from solid-devtools.

So in regards to the use of components on the target application, would it now allow users to debug by running the and components side by side if users no longer need to warp the application?

For instance, previously we needed to and have debugComponent() invoked inside the application to access updated root data for debugging purposes. With this new update, could we just do to access root data now? (I attached some screenshots below to show what I am referring to)

from solid-devtools.

I'm closing this for now, as this isn't the direction I'll be going currently.

from solid-devtools.