I just did a fresh init using mern-cli (the same problem exists when cloning mern-starter). When I ran npm install, I encountered the following errors between webpack and babel.

22283 error Windows_NT 6.2.9200 22284 error argv "c:\Program Files\nodejs\node.exe" "c:\Users\npaxton\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install" 22285 error node v4.4.7 22286 error npm v2.15.8 22287 error code EPEERINVALID 22288 error peerinvalid The package webpack@2.1.0-beta.19 does not satisfy its siblings' peerDependencies requirements! 22288 error peerinvalid Peer webpack-dev-server@2.1.0-beta.0 wants webpack@^2.1.0-beta 22288 error peerinvalid Peer chunk-manifest-webpack-plugin@0.1.0 wants webpack@^1.4.0-beta6 22288 error peerinvalid Peer babel-plugin-webpack-loaders@0.7.0 wants webpack@>=1.12.9 <3.0.0 22288 error peerinvalid Peer babel-loader@6.2.4 wants webpack@1 || ^2.1.0-beta 22288 error peerinvalid Peer extract-text-webpack-plugin@1.0.1 wants webpack@^1.9.11 22288 error peerinvalid Peer webpack-dev-middleware@1.6.1 wants webpack@1 || ^2.1.0-beta 22289 verbose exit [ 1, true ]

I tried updating Node and NPM to the latest, but that only resulted in some fresh npm 3+ errors. Is there a graceful way to correct this issue? I'm sure I've got a peer dependency wrong somewhere. The webpack@2.1.0-beta.19 is from my global node_module, not from the version specified in package.json.