Nodemon configuration does not allow for white spaces

Nobody has claimed this yet.

I'm currently running into the same issue as issue #59, where backpack cannot run because there are white spaces in the directory where I am executing the command. Please note that I'm running Windows 10.

I have reason to believe that the way that you configured Nodemon to run is at fault.

```
const startServer = () => {
const serverPaths = Object
.keys(serverCompiler.options.entry)
.map(entry => path.join(serverCompiler.options.output.path, `${entry}.js`))
nodemon({ script: serverPaths[0], watch: serverPaths, nodeArgs: process.argv.slice(2) })
.on('quit', process.exit)
}
```

If I hardcode nodemon to use **'./build/main'**, instead of **serverPaths[0]**, everything works fine. I could create a pull request but I'm not sure if that's the most elegant solution.

Start at the startServer function shown in the issue and inspect how serverPaths[0] is passed to nodemon. Reproduce the command on Windows with a project path containing spaces, then verify that the server starts successfully without hardcoding './build/main'.

Written by the indexing model from the issue text.