Nope, you have to create a debug in webstorm to hit server side breakpoints. The thing I find really annoying with this is you don’t get console errors when meteor fails to compile in webstorm. So you have to either stop the debug and do meteor run in the console or refresh your browser to see the compile time error.
Re the slowness, I haven’t tried webstorm’s live edit but because meteor triggers a recompile on all file edits (blank spaces included) you’ll always get the (10 secs for me) long refresh time. Even if live edit can refresh your html quickly, you’ll still get a double refresh when meteor finishes building. Especially for me since I’m using jade… this is why we’re holding out for 1.2