Feedback

Bugs, missing features, and "it doesn't work in my org" reports are all welcome — they decide what gets built next.

Report a bug

Email bikerthatcodes@gmail.com. The more of the following you can include, the faster it gets fixed:

What you expected, and what happened instead
The kind of page — record page, Lightning console, Experience Cloud site, Setup, Classic
Whether it was LWC highlighting, Aura highlighting, or both
Whether your org uses a namespace, and whether managed-package components are involved
Your Chrome version, from chrome://version
Anything logged in the browser console (F12 → Console)

Please don't send screenshots containing real customer data. A sandbox or a scratch org makes a much better bug report, and keeps your org's data where it belongs.

Request a feature

Email bikerthatcodes@gmail.com and describe the problem you're trying to solve rather than the solution you have in mind — it usually leads somewhere better. Knowing what you'd otherwise do by hand is the most useful detail you can give.

Already on the list

These are known and planned, so no need to report them:

Components in namespaced and managed-package orgs are not detected yet
Components inside closed shadow roots cannot be detected at all, by any extension
Standard base components (lightning-*, force-*) are not highlighted — this is deliberate for now, and will become an option
There is no Microsoft Edge listing yet

Leaving a review

If the extension is useful, a review on the Chrome Web Store genuinely helps other Salesforce developers find it. If it isn't useful, please email first — a bug is much easier to fix than a one-star rating is to undo.