Unable to debug using --inspect-brk (blank source code)

[gurupras]

When trying to debug using node --inspect-brk=0.0.0.0:9634 https-server.js --dev, the file https-server.js appears fine on my browser, however, the remaining files are all blank. As you can imagine, I'm having a really hard time debugging code.

https-server.js

The backend/server/server file referenced above has a debugger statement within it. The interpreter(?) correctly breaks at the debug point, however the code shows up blank.

Here are the versions I'm using:
node: v8.11.4
esm: 3.0.84
Chrome: Version 70.0.3538.110 (Official Build) (64-bit) (not sure if relevant)

[jdalton]

Hi @gurupras!

We do support debugging in the Chrome inspector (with file sources visible). This looks like a bug/regression in the Chrome inspector. If you could provide a simple repro repo I could see if I can reproduce it.

[gurupras]

I'm struggling to create a simple repo to reproduce this. I currently have a large project whose code I cannot share which is suffering from this bug. Let me see if I can do a git bisect to determine what caused this regression to occur. I recall I was able to debug just fine several months ago.

[gurupras]

Not sure if this helps at all, but everything works fine if I connect via Chrome on Windows (v71.0.3578.98). You're definitely right. It seems to be a problem with Chrome rather than esm.

[jdalton]

Cool!

You should totally file a bug on them. In my experience they’ve been pretty responsive.

[gtarsia]

This is working for me with chrome v75.0.3745.4 (dev branch).
But it's not working with Chrome Dev v73.0.3683.86 (stable branch).

Unfortunately the v75 version is also having problems to connect normally as explained here nodejs/node#23693.
So I have to connect manually to this url chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=localhost:9229/{token} with token being the token you get when you run node inspect (assuming 9229 is your port).

[june07]

https://blog.june07.com/nim-custom-devtools-url

May find NiM useful. The blog post above specifically answers how to continue using the most recent Chrome(or Chromium based... soon to be Edge.) browser whilst changing the DevTools version to a working one.

https://github.com/june07/NiM
https://chrome.google.com/webstore/detail/nodejs-v8-inspector-manag/gnhhdgbaldcilmgcpfddgdbkhjohddkj

[jdalton]

Related nodejs/node#26887 and https://bugs.chromium.org/p/chromium/issues/detail?id=941608.