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

[DevTools Bug]: Use console custom formatters #32555

Open
sroussey opened this issue Mar 9, 2025 · 0 comments
Open

[DevTools Bug]: Use console custom formatters #32555

sroussey opened this issue Mar 9, 2025 · 0 comments
Labels
Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug

Comments

@sroussey
Copy link

sroussey commented Mar 9, 2025

Website or app

https://ellmers-web.netlify.app/

Repro steps

Quick background: I was one of the Firebug developers back in the day, and I used JS frameworks and hated that the console and the entire debugging UI always showed things in a lower level of abstraction than the user was dealing with. So in 2011, I created the first extension to Firebug to put extra panels in the devtools like your Components tab does now (it supported ExtJS, Backbone, YUI, Ember, Angular, etc).

One of the hooks I put in, was to not just let devs like you add panels, but also update the look of the objects themselves. So if you logged a ExtJS component, you saw what looked like an ExtJS component. 14 years later, you log some react stuff and it looks like goobligook.

I begged Paul Irish and Chrome devs to put it in, and they did, though you need to activate it in the settings panel. Firefox followed with their own using the Chrome api, though I think their docs for it are better.

Creating your own formatters is far better than the console.group thing you do now which requires going to the Components panel first.

If you are curious how they work, you can go here: https://ellmers-web.netlify.app/ open the console and follow instructions. But this is what it looks like:

Image

Unfortunately, it only works in the console, where back in the day I had it working in the debugger as well where knowing what is what is actually more useful.

Thanks for taking the time to read this feature request.

PS: I have my own, though it would not have your distribution. When I tried, I could make the console objects get nice names and even mark with [memo] and show properties, but I don't know how to navigate the internals to get the other stuff that is shown in the Components tab like hooks and renderedBy.

Image

Here is what it looks like with custom formatters off:

Image

How often does this bug happen?

Every time

DevTools package (automated)

No response

DevTools version (automated)

No response

Error message (automated)

No response

Error call stack (automated)


Error component stack (automated)


GitHub query string (automated)


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug
Projects
None yet
Development

No branches or pull requests

1 participant