This seems to be still in active development phase
https://nodejs.org/api/inspector.html#integration-with-devtools.
https://sachinkasana.medium.com/http-2-network-inspection-in-node-js-debug-like-a-pro-3812fc3a7b67
For me it works with flag --experimental-network-inspection
with node v24
node --inspect-brk --experimental-network-inspection -e "fetch('https://google.com')"
Now in the chromium based browser type chrome://inspect then click the discovered target, then the Network tab in Chrome Dev Tools for node should show entries.
Broadcast stack may look like:
broadcastToFrontend @ VM79 node: inspector: 212
requestWillBeSent @ VM79 node: inspector: 216
onClientRequestStart @ VM108 network undici: 78
publish @ node: diagnostics channel: 156
Request @ VM117 undici: 2661
[dispatch] @ VM117 undici: 8499
dispatch @ VM117 undici:1993
[dispatch] @ VM117 undici: 2258
dispatch @ VM117 undici: 1993
[dispatch] @ VM117 undici:8963
dispatch @ VM117 undici:1993
(anonymous) @ YM117 undici:12153
dispatch @ VM117 undici:12153
httpNetworkFetch @ YM117 undici: 12053
httpNetwork0rCacheFetch @ VMA17 undici:11939
httpFetch @ YM117 undici:11772
schemeFetch @ VM117 undici:11689
mainFetch @ VM117 undici: 11533
fetching @ VM117 undici:11502
fetch @ VM117 undici: 11368
fetch @ VM117 undici:15843
fetch @ node: internal/bootstrap/web/exposed-window-or-worker:83
(anonymous) @ VM114 levaUl:1
runScriptInThisContext @ node: internal/vm:219
(anonymous) @ node:internal/process/execution:451
(anonymous) @ VM116 levall-wrapper: 6
runScriptInContext @ node: internal/process/execution: 449
evalFunction @ node: internal/process/execution:283
evalTypeScript @ node: internal/process/execution: 295
(anonymous) @ VM75 eval string:71