'Disable all existing AND future debugger statements?
How can I completely disable the stopping-on-debugger-statements feature of chrome devtools? I want to be able to put the devtols in a kind of operational mode where the semantics of debugger; is no-op. I am not interested in how to disable individual breakpoints and debugger statements. I am not interested in how to disable all breakpoints and debugger statements existing at the exact moment the solution is applied. I am interested in a solution that effectively globally redefines the meaning of debugger; to mean "do nothing, proceed as usual" - i.e. a solution that will successfully defeat scripts that actively insert debugger; statements in eval'd code in a setInterval() loop with the specific purpose of disabling devtools. "Never pause ANYWHERE, including code that you don't know about yet", as starkly opposed to mere "Never pause here".
Is this doable?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|