Boilerplate not starting in Windows 10 + Ubuntu

I’m using the following versions below: node: v8.11.3 npm: 5.6.0 yarn: 1.7.0

npm ERR! code ELIFECYCLE 
npm ERR! errno 1 
npm ERR! electron-react-boilerplate@0.13.3 start-main-dev: cross-env HOT=1 NODE_ENV=development electron -r babel-register ./app/main.dev.js 
npm ERR! Exit status 1 
npm ERR! 
npm ERR! Failed at the electron-react-boilerplate@0.13.3 start-main-dev script. 
npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 
 
npm ERR! A complete log of this run can be found in: 
npm ERR!     /home/gurbir/.npm/_logs/2018-06-27T23_36_19_493Z-debug.log 
npm ERR! code ELIFECYCLE 
npm ERR! errno 1 
npm ERR! electron-react-boilerplate@0.13.3 start-renderer-dev: cross-env NODE_ENV=development node --trace-warnings -r babel-register ./node_modules/webpack-dev-server/bin/webpack-dev-server --config webpack.config.renderer.dev.js 
npm ERR! Exit status 1 
npm ERR! 
npm ERR! Failed at the electron-react-boilerplate@0.13.3 start-renderer-dev script. 
npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 
 
npm ERR! A complete log of this run can be found in: 
npm ERR!     /home/gurbir/.npm/_logs/2018-06-27T23_36_19_607Z-debug.log 
npm ERR! code ELIFECYCLE 
npm ERR! errno 1 
npm ERR! electron-react-boilerplate@0.13.3 dev: cross-env START_HOT=1 node -r babel-register ./internals/scripts/CheckPortInUse.js && cross-env START_HOT=1 npm run start-renderer-dev 
npm ERR! Exit status 1 
npm ERR! 
npm ERR! Failed at the electron-react-boilerplate@0.13.3 dev script. 
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

10 silly lifecycle electron-react-boilerplate@0.13.3~dev: Args: [ '-c', 
10 silly lifecycle   'cross-env START_HOT=1 node -r babel-register ./internals/scripts/CheckPortInUse.js && cross-env START_HOT=1 npm run start-renderer-dev' ] 
11 silly lifecycle electron-react-boilerplate@0.13.3~dev: Returned: code: 1  signal: null 
12 info lifecycle electron-react-boilerplate@0.13.3~dev: Failed to exec dev script 
13 verbose stack Error: electron-react-boilerplate@0.13.3 dev: cross-env START_HOT=1 node -r babel-register ./internals/scripts/CheckPortInUse.js && cross-env START_HOT=1 npm run start-renderer-dev 
13 verbose stack Exit status 1 
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16) 
13 verbose stack     at emitTwo (events.js:126:13) 
13 verbose stack     at EventEmitter.emit (events.js:214:7) 
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 
13 verbose stack     at emitTwo (events.js:126:13) 
13 verbose stack     at ChildProcess.emit (events.js:214:7) 
13 verbose stack     at maybeClose (internal/child_process.js:925:16) 
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) 
14 verbose pkgid electron-react-boilerplate@0.13.3 
15 verbose cwd /mnt/c/Users/gurbir/Desktop/electron-react-boilerplate 
16 verbose Linux 4.4.0-17134-Microsoft 
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev" 
18 verbose node v8.11.3 
19 verbose npm  v5.6.0 
20 error code ELIFECYCLE 
21 error errno 1 
22 error electron-react-boilerplate@0.13.3 dev: cross-env START_HOT=1 node -r babel-register ./internals/scripts/CheckPortInUse.js && cross-env START_HOT=1 npm run start-renderer-dev 
22 error Exit status 1 
23 error Failed at the electron-react-boilerplate@0.13.3 dev script. 
23 error This is probably not a problem with npm. There is likely additional logging output above. 
24 verbose exit [ 1, true ]

[gurbirkalsi]

Got this working by doing the following on Windows and Ubuntu:

Windows:

$ npm install --global --production windows-build-tools
$ yarn
$ npm rebuild
$ npm run dev

Ubuntu:

$ sudo apt-get install build-essential clang libdbus-1-dev libgtk-3-dev \
                         libnotify-dev libgnome-keyring-dev libgconf2-dev \
                         libasound2-dev libcap-dev libcups2-dev libxtst-dev \
                         libxss1 libnss3-dev gcc-multilib g++-multilib curl \
                         gperf bison
$ yarn
$ npm rebuild
$ npm run dev

[DogByteMarketing]

For anyone else that runs into this issue, we just updated npm and node, but be warned of any applications you built using this latest node version unless otherwise specified in config.