Chrome Debugger since update 120: Breakpoints not working when using the "debugger" keyword

Question

Since the recent Chrome update to version 120, I've encountered a perplexing issue. When using the "debugger" keyword in my code to set a breakpoint, nothing happens. Initially, I suspected an issue on my macOS machine, but after updating Chrome on my PC, the same problem occurred. Has anyone else experienced this issue, or am I alone in this?

I've already submitted a "report," but it seems like throwing a message into the void. If anyone has insights on resolving this issue or has faced a similar situation, I would greatly appreciate any assistance. Thanks in advance!

Answer 1

Go to the Chrome DevTools settings and uncheck this exclusion rule:

p.s. As noted in the other answer, excluding based on filenames like /node_modules/ by default tends to disable debugging entirely in lots of contexts.