You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For debugging with Chrome Devtools, I think that it may be more useful in practice to replace debug and inspect with debug-brk and inspect-brk so that when running bmocha -d, the debugger pauses before running through all the tests. It seems to ignore my debugger statements when using inspect (the spawned process receives --inspect), but I can successfully open up the Chrome debugger and it stops at my debugger statements if I replace inspect with inspect-brk so that --inspect-brk is passed to the spawned process.
Simply making that change at the lines above breaks the normal debug argument. The Chrome debugger is a really nice tool but using the CLI debugger works well too
The text was updated successfully, but these errors were encountered:
OSX
For debugging with Chrome Devtools, I think that it may be more useful in practice to replace
debug
andinspect
withdebug-brk
andinspect-brk
so that when runningbmocha -d
, the debugger pauses before running through all the tests. It seems to ignore mydebugger
statements when usinginspect
(the spawned process receives--inspect
), but I can successfully open up the Chrome debugger and it stops at mydebugger
statements if I replaceinspect
withinspect-brk
so that--inspect-brk
is passed to the spawned process.bmocha/bin/bmocha
Lines 19 to 20 in fa38810
Simply making that change at the lines above breaks the normal
debug
argument. The Chrome debugger is a really nice tool but using the CLI debugger works well tooThe text was updated successfully, but these errors were encountered: