Skip to content

Migrate away from dedicated Aurelia tab to original approach of using Elements view and Aurelia tab #16

Closed

Description

@Vheissu

We currently maintain a separate Aurelia tab which introduces friction. Developers start in the Elements view and it already does a good job of keep tracking of things and we also have an Aurelia panel in the Elements view too. Someone raised this a little while ago and initially the dedicated Aurelia panel was intended to be more diagnostic purposes and whatnot, but for what we want it to be it makes sense to just use the Elements view. The original attempt was copying other extensions like the React devtools.

  • Remove top level Aurelia tab and de-duplicate logic
  • Clean up existing tests/components
  • Create dedicated new sidebar app for the extension to use in the Elements panel
  • Make Aurelia inspector tab show for all elements, not just found elements and avoid traversal closest Aurelia parent logic
  • Allow quick searching for components and click to view in DOM
  • Speed up detection logic
  • Component hierarchy
  • Add e2e tests
  • Revise existing unit tests
  • Ensure it works for both Aurelia 1 and Aurelia 2 apps

Activity

  1. self-assigned this
    on Nov 27, 2025
  2. Vheissu commented on Dec 1, 2025

    @Vheissu
    MemberAuthor

    Closed by #17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions