CD

Cloudflare Developers•2y ago•

1 reply

niels7

Is there something special you need to

Is there something special you need to do to get local Chrome DevTools profiling working properly? I'm trying the following (with wrangler 3.22.3):

* wrangler dev -e test --port 8787wrangler dev -e test --port 8787
* push 'd' to open chrome devtools, which opens https://devtools.devprod.cloudflare.dev/js_app?theme=systemPreferred&ws=127.0.0.1%3A9229%2Fws&domain=(REDACTED)&debugger=true * Confirm source files appear under "Sources" tab * in devtools->Profiler, click start * send a request to the local port, confirm the request appears in the devtools network tab * stop profiling * All I see in the CPU profile is (program), without any detail on the actual function calls (see screenshot) * I get the same result if I try https://devtools.devprod.cloudflare.dev/js_app?theme=systemPreferred&ws=127.0.0.1%3A9229%2Fws&domain=(REDACTED)&debugger=true * Confirm source files appear under "Sources" tab * in devtools->Profiler, click start * send a request to the local port, confirm the request appears in the devtools network tab * stop profiling * All I see in the CPU profile is (program), without any detail on the actual function calls (see screenshot) * I get the same result if I try chrome://inspect` and then "Open dedicated DevTools for Node" (see 2nd screenshot)