Using a `debugger;` statement allows you to trigger a breakpoint with code. This only gets activated when the devtools window is opened, so placing this statem

Using a `debugger;` statement allows you to trigger a breakpoint with code. This only gets activated when the devtools window is opened, so placing this statement in a frequently executed piece code will continuously interrupt whatever you are doing in the devtools when you use them. I assume in the past the tooling might not have had the necessary configuration options to suppress that, but nowadays you can just disable debugger statement breakpoints to avoid it.