In the same way a user can TURN ON break points, or add conditions to breakpoints, may I suggest being able to add conditions to debugger statements or disable them individually?
(In reply to Frazer from comment #0) > In the same way a user can TURN ON break points, or add conditions to > breakpoints, > may I suggest being able to add conditions to debugger statements or disable > them individually? What is the use case that this enables, which is not currently possible? Can't you just add breakpoints if you don't want `debugger` to always pause? This would be a nontrivial project as `debugger` compiles into a byte code that pauses the debugger. It is not really related to the existing breakpoints system.