Bug: "Sources" panel is empty in inspector

[marvinhagemeister]

The "Sources" panel in the Chrome DevTools inspector is empty. This makes it impossible to continue when running with --inspect-brk. Tried to do a bisect but it seems like all Deno versions are affected. Maybe Chrome changed something on there side?

Steps to reproduce

1. Run deno init
2. Run deno run -A --inspect-brk main.ts
3. In Chrome, go to chrome://inspect
4. Click on "Inspect" link

Version: Deno 1.45.5

[marvinhagemeister]

Can confirm that this is an upstream issue in DevTools, see https://issues.chromium.org/issues/342961829?pli=1

[bartlomieju]

@devsnek mentions that it might be because we set "opaque" origins for all scripts. Gus has a branch that is supposed to fix it.

[devsnek]

The upstream bug has been marked fixed and I verified that I can use --inspect-brk with a chromium 129 nightly build, so I think you just need to wait for that fix to be available in your chrome install.

[june07]

Another PSA about a solid workaround for this and other instances where DevTools on the current browser release is broken in some way...

Use Node --inspector Manager the Chromium browser extension (I am the author)

I just resolved a different DevTools issue just a few days ago (see here).

NiM allows you to mix/match DevTools versions with whatever browser version you happen to be running, so when bugs become showstoppers, it's just a matter of selecting a different DevTools version from NiM's settings which can be hosted locally as shown in the example below or from any other endpoint:

• NiM's https://devtools-frontend.june07.com/inspector.html
• Google's Appspot https://chrome-devtools-frontend.appspot.com
• Whatever other devtools-frontned endpoint you want

Quick change in the settings to swap DevTools vs needing to install Canary or wait:

Showing me debugging Deno as per @marvinhagemeister steps

[marvinhagemeister]

With the recent Chrome 128.0.6613.114 update I cannot reproduce this issue anymore. Looks like they backported the fix.