The biggest sell for Webstorm is their debugger, except it doesn’t work for Packages! I created an issue for it in April: https://youtrack.jetbrains.com/issue/WEB-16337 and lots of Meteor developers +1ed it but they still haven’t gotten to it.
All my work is in packages, so Webstorm debugging is a no go for me–none of the other Webstorm features do anything for me; and its heaviness, cluttered appearance are a major turn off. I rather use Sublime if I’m not going to get something fancy like Debugging. So I use Sublime + Node Inspector. Not inspector itself is surprisingly crappy itself, but as the best option it least gets the job done.
I’ve been shocked at how low quality debugging is in the Node world. There’s a lot of minor bugs in Node-Inspector. Debugging needs to be truly solved for the Node world first; and one day hopefully we can get a super client+server meteor-specific debugging solution as well. Clearly, the real problem is the market: developers don’t use debugging as much as they should. It’s just not something you get into your first year or 2 as a developer. And even then, due to the more synchronous nature of the server (particularly for us Meteor devs using fibers vs regular Node devs) debugging only ends up being a client side activity; the reason being eventually we get fed up trying to fix something and resolve to the chrome debugger since we are already in the console, which when errors are thrown will link you directly to where you should put a breakpoint. So that’s a lot more natural on the client.
If on the server we can figure out how to make debugging a lot easier, a lot more natural, and perhaps deeply integrated into the specific tools you’re using (e.g. Meteor), we’d get better debuggers. But that’s a chicken and the egg problem. Basically someone gotta come along and make building a node debugger a priority. As it is, node-inspector is basically a hacked-together version of the chrome debugger repurposed for server side code. Not that that is necessarily a bad path, but it says a lot about how seriously we developers are taking it–it’s not like you see a “Node Debugger” company, and that’s all they do.
Anyway, one day…