mern-starter: "Cannot find module" when running npm start for v2.0.0 on Windows 10
Hi all, I am running Node v6.2.2 and npm 3.9.6 on Windows 10 Preview build 14366.
I did a clean install of the starter repo - both by cloning the repo and also using the CLI, which apparently now uses v2.0.0. When I hit “npm start” I get the following error. It seems like there is some issue with how file paths are setup.
I’m new to the JavaScript tooling space so I’m not sure how to debug. Any thoughts or workarounds would be appreciated.
module.js:442
throw err;
^
Error: Cannot find module 'C:\Users\Jacob\OneDrive\Documents\mern-app\C\:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\webpack\bin\webpack.js'
at Function.Module._resolveFilename (module.js:440:15)
at Function.Module._load (module.js:388:25)
at Module.runMain (module.js:575:10)
at run (node.js:348:7)
at startup (node.js:140:9)
at node.js:463:3
C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-core\lib\transformation\file\index.js:591
throw err;
^
Error: C:/Users/Jacob/OneDrive/Documents/mern-app/client/modules/App/App.js: Command failed: node C\:\\Users\\Jacob\\OneDrive\\Documents\\mern-app\\node_modules\\webpack\\bin\\webpack.js C\:\\Users\\Jacob\\OneDrive\\Documents\\mern-app\\client\\modules\\App\\App.css C\:\\Users\\Jacob\\AppData\\Local\\Temp\\.webpack.res.1466494094898_296377.js --config ./webpack.config.babel.js --bail
module.js:442
throw err;
^
Error: Cannot find module 'C:\Users\Jacob\OneDrive\Documents\mern-app\C\:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\webpack\bin\webpack.js'
at Function.Module._resolveFilename (module.js:440:15)
at Function.Module._load (module.js:388:25)
at Module.runMain (module.js:575:10)
at run (node.js:348:7)
at startup (node.js:140:9)
at node.js:463:3
at checkExecSyncError (child_process.js:486:13)
at execSync (child_process.js:526:13)
at exports.default (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-plugin-webpack-loaders\lib\runWebPackSync.js:41:51)
at PluginPass.CallExpression (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-plugin-webpack-loaders\lib\plugin.js:93:60)
at newFn (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\visitors.js:310:19)
at NodePath._call (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\path\context.js:78:18)
at NodePath.call (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\path\context.js:49:17)
at NodePath.visit (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\path\context.js:108:12)
at TraversalContext.visitQueue (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\context.js:174:16)
at TraversalContext.visitSingle (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\context.js:124:19)
at TraversalContext.visit (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\context.js:219:19)
at Function.traverse.node (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\index.js:171:17)
at NodePath.visit (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\path\context.js:118:43)
at TraversalContext.visitQueue (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\context.js:174:16)
at TraversalContext.visitMultiple (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\context.js:119:17)
at TraversalContext.visit (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\context.js:217:19)
at Function.traverse.node (C:\Users\Jacob\OneDrive\Documents\mern-app\node_modules\babel-traverse\lib\index.js:171:17)
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 6
- Comments: 23 (11 by maintainers)
@SOSANA Merged. 👍
@SOSANA Awesome! @somus You’re welcome!
Same issue here, error is coming from babel-plugin-webpack-loaders.
It use node-shell-quote to generate
node C\:\\Users\\Jacob\\OneDrive\\Documents\\mern-app\\node_modules\\webpack\\bin\\webpack.jsand this definitly cannot work in a windows command process.Nice work @SOSANA! 👍
@arguser to fix your issue with peerDependencies, please update npm up to 3.0 with
npm install -g npm@nextand try again 😃