Repository navigation
Conversation
…omponent funneling
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an interactive Element Inspector and cross-panel component funneling to the devtools dock.
Rather than only serving as a jump-to-editor utility, selecting an element activates a component funnel across the devtools panels:
/__open-in-editor), and a clear button (✕) to unfunnel.Alt+Shift+C(or the crosshair icon in the dock header) toggles inspect mode.Escapecancels inspection.Technical Details
@solidjs/vite-plugin's dev-modelocationinjection (owner._component.fn.location) and Solid's runtime ownership tree.document.createElement/createElementNSin dev mode using aWeakMap<Node, Owner>to map real DOM nodes back to their originating Solid component owners without adding data-attributes to the user's DOM.ReactivityViewerfilters nodes usingisDescendantOf(node.owner, targetOwner)so multiple instances of identical components (like<For>iterations or reused UI components) are isolated accurately.launch-editor-middleware.Showcase
Verification
src/dev-toolbar/inspector/lookup.test.ts).pnpm test(all 116 tests passing).pnpm typecheck(clean TypeScript check).pnpm format:check(oxfmt clean).pnpm build(clean rolldown bundle & DTS generation)..changeset/element-inspector.md).