While working as a full stack developer, I'm using node for most of my server-side application at both work and home. At the end of 2014 I got tired of all breaking changes with most of the npm modules and I was in a position where I was having few projects, which were using some npm modules as a backbone of the app and those modules had breaking changes at some point. Every new project was using the new releases, but the old ones didn't. I had to move through the github release tags, follow the changes, different versions of the documentations, which is okay, if it was an application or two but with more, the time spent was huge, and in early 2015 I decided to create my own wrapper.
It's important to say that I've used most of the frameworks out there, like: Express, Sails, Hapi, Loopback, but non of them fits my needs. They're really good in what they do.
But I needed something more aggresive than Express, with better performance from Sails and with less configuration comparing to Loopback
I also needed a daemon, which will restart my server on file change, a debugger and a linter. I also wanted to skip the moment when I'm adding all of the dependencies above in package.json. I didn't want global packages, because we all know how bad this is when using multiple work stations. And I needed a possibility to create different types of servers in the same application withouth having to bother myself with "where and how", and fits for IoT
