I've just upgraded my Chrome to 73.0.3683.75 (Linux) and now cannot get my dedicated Node debugger to actually debug a running instance. Even though I can see the "Debugger attached" message in the console:
$ node --inspect-brk hello.js
Debugger listening on ws://127.0.0.1:9229/864a1c18-5e45-49ab-843c-77a22841ffff
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
the debugger window does not show any signs of debugging a target:
Anyone has an idea if this is broken in Chrome 73 or if I'm doing something wrong? Thanks!
Yes, it's a bug with v73. I am also seeing it
https://bugs.chromium.org/p/chromium/issues/detail?id=941608&q=nodeJS
Update
This bug was fixed in chrome 74.0.3729.61 check here
you might use ndb which is tailored for node.js and also from GoogleChromeLabs.
install using
npm install -g ndb
Usage:
Use ndb instead of node command:
ndb server.js
# Alternatively, you can prepend `ndb`
ndb node server.js
Prepend ndb in front of any other binary:
ndb npm run unit
ndb mocha
ndb npx mocha
Launch ndb as a standalone application:
# cd to your project folder (with a package.json)
ndb .
# In Sources panel > "NPM Scripts" sidebar, click the selected "Run" button
if you are using nodemon:
ndb nodemon .
for further details see the project github repository
来源：https://stackoverflow.com/questions/55143498/chrome-73-can-no-longer-debug-nodejs-with-dedicated-devtools-for-node