I’ve got this KINDA working for a meteor 1.2 app using the latest WebStorm. I fired up my project with:
meteor run --debug-port 5858
Once it’s up and awaiting a connection from the debugger, I start my debugger in WebStorm as a Node remote debugger on port 5858.
Cool.
It does indeed stop on breakpoints, but it gets confused if I step through. It clearly doesn’t track the source quite right, although the variable watching seems ok.
This is after killing an afternoon trying various alternatives and setups with and without WebStorm. I’ve been coding a long, long time and basic debug support is critical to productivity; console.log doesn’t cut it, but it seems to be the most trustworthy means to see what’s up. Please show me I’m wrong.