Using 'debugger' to help in javascript debugging

Re:Using 'debugger' to help in javascript debugging by artursapek on Monday February 18, 2013 @03:21PM (#5240382)

Chrome Dev Tools also lets you ignore breakpoints, but I hope you're not suggesting to ship code with debugger statements?

[ Parent | on HN ]

Re:Using 'debugger' to help in javascript debugging by k3n on Monday February 18, 2013 @04:24PM (#5240761)

I don't it'll be much of a concern in a few years, though we're not there yet. Currently, Chrome will just gloss over any debugger statements unless the dev tools is open; if others happen to follow suit, then leaving a debugger statement in won't have any side-effects.

[ Parent | on HN ]

Re:Using 'debugger' to help in javascript debugging by rco8786 on Monday February 18, 2013 @04:47PM (#5240950)

Still a really bad practice, IMO

[ Parent | on HN ]

Re:Using 'debugger' to help in javascript debugging by artursapek on Monday February 18, 2013 @06:01PM (#5241381)

I know, but leaving rogue debuggers after you're done using them is not good practice.

[ Parent | on HN ]

Re:Using 'debugger' to help in javascript debugging by nathanstitt on Tuesday February 19, 2013 @01:57PM (#5246273)

Sorry if I gave that impression! What I meant to refer to was that you can insert them somewhere in a loop and then disable it once the loops ran a few times rather than having to press continue (potentially) several hundred times.

[ Parent | on HN ]

Re:Using 'debugger' to help in javascript debugging by artursapek on Tuesday February 19, 2013 @09:26PM (#5248609)

Ah, yes. That is useful

[ Parent | on HN ]