News for hackers. Stuff that matters.

A comment on How to Inspect React Server Component Activity with Next.js and OpenTelemetry. Parent comment

Re:How to Inspect React Server Component Activity with Next.... by sroussey on Thursday January 23, 2025 @06:37AM (#42803023)
And these days, you use the same browser debug tools to attach to nodejs.
[ Parent | on HN ]
Re:How to Inspect React Server Component Activity with Next.... by mmanciop on Thursday January 23, 2025 @07:18AM (#42803260)
For local development, yes. But I see that almost never done in production settings, especially with containerized workloads. Is there a neat way to do it in Kubernetes?
[ Parent | on HN ]
Re:How to Inspect React Server Component Activity with Next.... by sroussey on Thursday January 23, 2025 @07:44AM (#42803426)
Well, I suggest never enabling the debugger in production.

But if you meant a local or dev server where you start node with --inspect then the port to forward is 9229 by default.

[ Parent | on HN ]
Re:How to Inspect React Server Component Activity with Next.... by sesm on Thursday January 23, 2025 @09:03AM (#42804096)
Yes, but it's missing the network tab, see https://github.com/nodejs/diagnostics/issues/75
[ Parent | on HN ]