Updated NPM and Webpack configuration to overcome installation errors

[ltfschoen]

Updated NPM dependencies and Webpack config to so can just run npm install without encountering installation any major errors that I encountered such as the following:

$ npm install
npm WARN [email protected] requires a peer of react@* but none was installed.
npm WARN [email protected] requires a peer of react-dom@* but none was installed.

$ npm run serve
sh: webpack-dev-server: command not found

$ npm install -g webpack-dev-server
npm WARN [email protected] requires a peer of webpack@>=1.3.0 <3 but none was installed.
npm WARN [email protected] requires a peer of webpack@1 || ^2.1.0-beta but none was installed.
...
Error: Cannot find module 'webpack'
Error: Cannot find module 'babel-polyfill'

ERROR in multi main
Module not found: Error: Cannot resolve module 'babel' 
...
ERROR in ./src/js/app.js
Module not found: Error: Cannot resolve module 'aframe'
...

[reidblomquist]

+1 - just updated my fork to latest master and tried running yarn and am running into the peer dependency errors (able to run serve - but yeh...)

update: just merged @ltfschoen's branch with these changes and ran with yarn - everything works fine! contemplating opening a pr that uses webpack-dashboard for dev if that sounds like a nicety maintainers would like.

[ngokevin]

What's graceful/lodash/minimatch for?

[ngokevin]

Can format

{
  plugins: ['syntax-jsx'],
  presets: ['es2015', 'react', 'babel-preset-stage-0']
}

[nobodysfool]

No