Cut down dependencies and lock them

[acontreras89]

Most times, after cloning the repository and running npm install I simply cannot start working right away.

I just spent an hour trying to figure out how to solve some really weird issues (an example can be found below) and, at the end, it was as simple as locking down the versions of the development dependencies.

When we discussed this matter before building the base applications, we decided to use the ^ notation to always have compatible versions installed. However, even though npm packages must adhere to semver, maintainers are showing themselves unable to determine when new changes are backwards-compatible or not.

In my opinion, this is due to the great amount of dependencies we currently have, so I would vote for lowering this number as well.

Example of a random error (which is thrown when trying to reach the development server through the browser):

webpack: wait until bundle finished: /js/index.html
FetchError: request to http://localhost:3000/js/index.html failed, reason: socket hang up
    at ClientRequest.<anonymous> (/home/aaron/redradix/projects/gmv/fop/client/node_modules/node-fetch/index.js:125:11)
    at emitOne (events.js:90:13)
    at ClientRequest.emit (events.js:182:7)
    at Socket.socketOnEnd (_http_client.js:342:9)
    at emitNone (events.js:85:20)
    at Socket.emit (events.js:179:7)
    at endReadableNT (_stream_readable.js:913:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Other examples of errors that we got after installing the base app were reported in #16, #17 and #18, all of them caused by outdated/unlocked dependencies.