Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could Ember Inspector deobfuscate component names? #2469

Open
backspace opened this issue Sep 20, 2023 · 2 comments
Open

Could Ember Inspector deobfuscate component names? #2469

backspace opened this issue Sep 20, 2023 · 2 comments

Comments

@backspace
Copy link

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:

Boxel 2023-09-20 15-48-19

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
Copy link
Member

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
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants