Nodejs Inspector not stopping at breakpoints

[govindrai]

I have the debugger keyword placed in multiple places in my file, and have even added manual breakpoints in the inspector UI. Still, executing the file does not stop at any breakpoints. I am using node 9.2.0 and chrome 64.0.3282.167.

Here is a picture of how my devtools appears.

[alexkozy]

What flag do you use to start Node with inspector? --inpsect or --inspect-brk?

[govindrai]

@ak239 I ran it with --inspect. --inspect-brk makes it work! If you have the time, could you explain why the inspector cannot pick up breakpoints without it? Super appreciate your quick reply!

[alexkozy]

We are working on better workflow here but for now --inspect-brk is only one way.
With --inspect-brk node waits DevTools frontend connection. On connection DevTools send all breakpoints information and starts JavaScript execution in node.
With --inspect node starts JavaScript execution without waiting for DevTools frontend. As soon as DevTools connected, we send the same breakpoint information to node but it can be too late since some JavaScript is already executed.

[govindrai]

Thank you for you help! Closing this!

Update as of 12/27/2018: All comments below are unrelated to my issue, but the title of this issue was relevant so it generated some comments. They were some breaking builds where inspect-brk was not working, but is now resolved. It seemed that the debugger was buggy :D.

However, the overarching solution still holds: Use inspect-brk to ensure breakpoints are not missed.

[tasoss]

Hello.
Because of the fact that inspect brk doesn't work , what do u propose?
I mean this thing used to work and it was great.It's really hard to debug on big projects.
Does changing node or chrome can solve this so at least,i will be able to debug?
Thanks!

[paramsinghvc]

What's the solution here. Why is it closed?
@ak239 Can you please suggest some workaround for the same. The debugger is not pausing on the breakpoints in chrome devtool.

[llwanghong]

run into the same issue, seems can only use vscode debug or downgrade chrome browser version.

…

On Wed, Nov 28, 2018 at 3:42 PM Parminder Singh ***@***.***> wrote: What's the solution here. Why is it closed? @ak239 <https://github.com/ak239> Can you please suggest some workaround for the same. The debugger is not pausing on the breakpoints in chrome devtool. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#85 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFSCSbWehZaF8yZPdGxVSp3fehU-9Go5ks5uzj5dgaJpZM4STuBR> .

[paramsinghvc]

In Chrome Canary 72, it works. @llwanghong

[viksok]

Updated to Chrome 72.0.3626.96 /Ubuntu yesterday and it stopped working.
Neither --inspect nor --inspect-brk doesn't work.

[Gobliins]

Missing breakpoints sometimes on Win Chrome Version 72.0.3626.109 (Official Build) (64-Bit)

[june07]

https://blog.june07.com/nim-custom-devtools-url explains a solution to this. Often the problem is due to breaking changes with DevTools. Using NiM allows you to lock the DevTools version whilst still using the most recent version of Chrome.

[alexkozy]

I suggest to use latest Chrome DevTools and file a bug on crbug.com when something does not work. In this case you get all new features and help other developers to get best experience.

Latest Node 12 should work well with latest Chrome DevTools frontend. Here is a link how to use dedicated devtools frontend: https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27

[june07]

Couldn't agree with @ak239 more.

With NiM I can use DevTools latest or a different version if I need, so while I'm filing my bug on crbug.com, I'm not blocked and can continue my own work:

I like using the latest and greatest version of DevTools whenever possible because the DevTools team is always improving it! As Paul brings out in the Youtube link ak239 shared: https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27, tools like NiM simply help in using the Chrome DevTools workflow.