Love the built-in Node.js debugging feature! Thanks guys!
That said, everytime I start my app the debugger repeatedly stop inside Node's built-in filesystem module code (fs.js) even though I do not have any breakpoints. For example, here are the first few lines of the file I'm running:
var path = require('path'),
express = require('express'),
The call to require('express') causes Node to eventually load a 3rd-party library from the filesystem, so the execution ends up in fs.js. This is where the debugger hits some sort of "invisible breakpoint", on fs.js:413.
If I keep clicking "Resume" the debugger advances but inevitably hits another "invisible breakpoint" in fs.js, sometimes at different lines.
The work-around I'm using is to mute all breakpoints until my app has finished launching, then un-mute. But this does seem like it might be a WebStorm-related bug. For comparison, I don't have this issue with the 'node-inspector' tool that can also be used for debugging, hence my suspisions that it's specific to WebStorm.
Any ideas? Thanks!