it is cool to see chrome devtools finally leaning into agents for the node stack.
i just hope this handles circular references better than the basic console log ever did.
are you seeing any significant memory overhead when running these experimental tools on a larger production sized codebase?
it is cool to see chrome devtools finally leaning into agents for the node stack.
i just hope this handles circular references better than the basic console log ever did.
are you seeing any significant memory overhead when running these experimental tools on a larger production sized codebase?
unfortunately, , i see :)