Could Ember Inspector deobfuscate component names?

[backspace]

Is your feature request related to a problem? Please describe.

I noticed when looking at a production deployment names that the component names were obfuscated, which is likely to be a compression artefact:

Describe the solution you'd like

Could Ember Inspector detect the component name from the source maps somehow, if they exist?

Describe alternatives you've considered

In our case we’ll probably look for whatever production build setting is causing this obfuscation and turn it off.

---

Thanks for the ongoing work on this, it’s still indispensable after all these years 🤩

[RobbieTheWagner]

Inspector relies on methods on Ember to give us the tree. I am not sure if we could somehow match what it gives us up with sourcemaps or not.

[patricklx]

I think at least glimmer could provide the names as specified in the template and not only extract it from the component instance

[NullVoxPopuli]

for how we want to solve this (perhaps via babel config), we'd also end up solving the "unknown template-only component" thing we see in development

[patricklx]

its already in ember-template-imports https://github.com/ember-cli/ember-template-imports/blob/master/src/babel-plugin.js
i could not get it into the babel template compilation. but looks like there is some work on glimmer-vm to get better support for this

[NullVoxPopuli]

ya -- so we're probably waiting on the great repo merge before that's all unblocked