Cannot run npm run build or npm start
10,789
Try deleting the node_modules
, and then run the script.
Author by
Nims
Updated on June 18, 2022Comments
-
Nims almost 2 years
Whenever I try building my web-pack file or starting web-pack dev server I get an error. It was working, but I was messing around with eslint and broke something.
This is the error package when trying
npm build
0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'prebuild', 'build', 'postbuild' ] 5 info lifecycle [email protected]~prebuild: [email protected] 6 silly lifecycle [email protected]~prebuild: no script for prebuild, continuing 7 info lifecycle [email protected]~build: [email protected] 8 verbose lifecycle [email protected]~build: unsafe-perm in lifecycle true 9 verbose lifecycle [email protected]~build: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/Nims/Documents/Web Development/Projects/React bookstore/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin 10 verbose lifecycle [email protected]~build: CWD: /Users/Nims/Documents/Web Development/Projects/React bookstore 11 silly lifecycle [email protected]~build: Args: [ '-c', 'webpack' ] 12 silly lifecycle [email protected]~build: Returned: code: 1 signal: null 13 info lifecycle [email protected]~build: Failed to exec build script 14 verbose stack Error: [email protected] build: `webpack` 14 verbose stack Exit status 1 14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16) 14 verbose stack at emitTwo (events.js:106:13) 14 verbose stack at EventEmitter.emit (events.js:191:7) 14 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14) 14 verbose stack at emitTwo (events.js:106:13) 14 verbose stack at ChildProcess.emit (events.js:191:7) 14 verbose stack at maybeClose (internal/child_process.js:886:16) 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) 15 verbose pkgid [email protected] 16 verbose cwd /Users/Nims/Documents/Web Development/Projects/React bookstore 17 verbose Darwin 16.5.0 18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build" 19 verbose node v6.10.3 20 verbose npm v4.5.0 21 error code ELIFECYCLE 22 error errno 1 23 error [email protected] build: `webpack` 23 error Exit status 1 24 error Failed at the [email protected] build script 'webpack'. 24 error Make sure you have the latest version of node.js and npm installed. 24 error If you do, this is most likely a problem with the setup package, 24 error not with npm itself. 24 error Tell the author that this fails on your system: 24 error webpack 24 error You can get information on how to open an issue for this project with: 24 error npm bugs setup 24 error Or if that isn't available, you can get their info via: 24 error npm owner ls setup 24 error There is likely additional logging output above. 25 verbose exit [ 1, true ]
and when trying npm start
0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle [email protected]~prestart: [email protected] 6 silly lifecycle [email protected]~prestart: no script for prestart, continuing 7 info lifecycle [email protected]~start: [email protected] 8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true 9 verbose lifecycle [email protected]~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/Nims/Documents/Web Development/Projects/React bookstore/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin 10 verbose lifecycle [email protected]~start: CWD: /Users/Nims/Documents/Web Development/Projects/React bookstore 11 silly lifecycle [email protected]~start: Args: [ '-c', 'webpack-dev-server' ] 12 silly lifecycle [email protected]~start: Returned: code: 1 signal: null 13 info lifecycle [email protected]~start: Failed to exec start script 14 verbose stack Error: [email protected] start: `webpack-dev-server` 14 verbose stack Exit status 1 14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16) 14 verbose stack at emitTwo (events.js:106:13) 14 verbose stack at EventEmitter.emit (events.js:191:7) 14 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14) 14 verbose stack at emitTwo (events.js:106:13) 14 verbose stack at ChildProcess.emit (events.js:191:7) 14 verbose stack at maybeClose (internal/child_process.js:886:16) 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) 15 verbose pkgid [email protected] 16 verbose cwd /Users/Nims/Documents/Web Development/Projects/React bookstore 17 verbose Darwin 16.5.0 18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" 19 verbose node v6.10.3 20 verbose npm v4.5.0 21 error code ELIFECYCLE 22 error errno 1 23 error [email protected] start: `webpack-dev-server` 23 error Exit status 1 24 error Failed at the [email protected] start script 'webpack-dev-server'. 24 error Make sure you have the latest version of node.js and npm installed. 24 error If you do, this is most likely a problem with the setup package, 24 error not with npm itself. 24 error Tell the author that this fails on your system: 24 error webpack-dev-server 24 error You can get information on how to open an issue for this project with: 24 error npm bugs setup 24 error Or if that isn't available, you can get their info via: 24 error npm owner ls setup 24 error There is likely additional logging output above. 25 verbose exit [ 1, true ]
Here is my webpack file
module.exports = { entry: ['babel-polyfill', './app/index.js'], output: { path: __dirname + '/build', // if the above line does not work, try `path: __dirname + '/build'` filename: 'bundle.js' }, module: { loaders: [ { test: /\.js$/, // a regular expression that catches .js files exclude: /node_modules/, loader: ['babel-loader'] } ], }, devServer: { port: 3000, // most common port contentBase: './build', inline: true } };
It seems its not picking up the local scripts in my webpack.config.js file - but I'm new to this and I'm still learning