Oleksandr Shybystyi

@hinews can you give more details about when do you get this exception? e.g. I have mongo 3.0.3, I run `node ./node_modules/mongo-migrate -runmm` - and don't get that exception.

running grunt with `--verbose` helped to notice the possible source of the bug. Well I've noticed that there is a delay between watch task prints `Completed in 1.142s at Mon...

what about `DEBUG=server grunt` ?

In case you're using `DEBUG=server grunt` you're also need to modify **./bin/www** (if you've generated project using express-generator), so it contains line `debug.log = console.log.bind(console);` so debug module sends messages...

I think that is 'by design' (hard to explain though). A workaround for this is to use grunt-concurrent, e.g. you can see an example of usage [here](https://www.npmjs.com/package/grunt-concurrent#logconcurrentoutput). Haven't tried it...