Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
565 views
in Technique[技术] by (71.8m points)

node.js - Chrome 73: Can no longer debug NodeJS with Dedicated DevTools for Node

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: Dedicated Node debugger window

Anyone has an idea if this is broken in Chrome 73 or if I'm doing something wrong? Thanks!

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Reply

0 votes
by (71.8m points)

Yes, it's a bug with v73. I am also seeing it

https://bugs.chromium.org/p/chromium/issues/detail?id=941608&q=nodeJS


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
OGeek|极客中国-欢迎来到极客的世界,一个免费开放的程序员编程交流平台!开放,进步,分享!让技术改变生活,让极客改变未来! Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...