NodeJS Debugging - Debugger stopping in require()'ed module, even if no breakpoints

Hello all,

I am attempting to debug my NodeJS application with Webstorm 10, however every time I start the debugger, it opens up a JS file in a node_module I am using and pauses, despite the fact that I have no breakpoints set in that file.

I'm assuming it's picking up a thrown exception in a module that is being later caught, similar to how Visual Studio does, but I am not sure. The line doesn't seem to be doing anything special.

Is there a way I can stop this from happening, while still allowing me to step into it if nessecary? Even if this means telling NodeJS to ignore those files?



1 comment
Comment actions Permalink

Please open Run/View Breakpoints dialog - do you have any breakpoints enabled there?


Please sign in to leave a comment.