silly lifecycle error when building Next.JS project - node.js

I recently started to learn Next/React to make a personal website, I'm trying to build a website with Next.JS, the website looks and works fine when running npm run dev, however, it's giving me an error when I try to make a build of it. I don't really understand the error, and much less how to fix it.
Thanks
Terminal Log
> portfolio# build C:\Users\Simon\Desktop\#Documents\##Projects\Coding\#web\portfolio
> next build
info - Checking validity of types
./pages/blog/[slug].js
26:17 Warning: Do not include stylesheets manually. See: https://nextjs.org/docs/messages/no-css-tags. #next/next/no-css-tags
./pages/index.js
12:9 Warning: Do not include stylesheets manually. See: https://nextjs.org/docs/messages/no-css-tags. #next/next/no-css-tags
13:9 Warning: External synchronous scripts are forbidden. See: https://nextjs.org/docs/messages/no-sync-scripts. #next/next/no-sync-scripts
23:13 Warning: Do not use <img>. Use Image from 'next/image' instead. See https://nextjs.org/docs/messages/no-img-element. #next/next/no-img-element
./components/MDXComponents.js
4:1 Warning: Assign object to a variable before exporting as module default import/no-anonymous-default-export
info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
info - Creating an optimized production build ...events.js:292
throw er; // Unhandled 'error' event
^
Error: EPERM: operation not permitted, open 'C:\Users\Simon\Desktop\#Documents\##Projects\Coding\#web\portfolio\.next\trace'
Emitted 'error' event on WriteStream instance at:
at C:\Users\Simon\Desktop\#Documents\##Projects\Coding\#web\portfolio\node_modules\next\dist\compiled\#vercel\nft\index.js:1:287421
at C:\Users\Simon\Desktop\#Documents\##Projects\Coding\#web\portfolio\node_modules\next\dist\compiled\#vercel\nft\index.js:1:287860
at FSReqCallback.oncomplete (fs.js:171:23) {
errno: -4048,
code: 'EPERM',
syscall: 'open',
path: 'C:\\Users\\Simon\\Desktop\\#Documents\\##Projects\\Coding\\#web\\portfolio\\.next\\trace'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! portfolio# build: `next build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the portfolio# build 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! C:\Users\Simon\AppData\Roaming\npm-cache\_logs\2021-11-13T12_14_00_615Z-debug.log
Log File
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Users\\Simon\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\Simon\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'build'
1 verbose cli ]
2 info using npm#6.14.12
3 info using node#v14.16.1
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle portfolio#~prebuild: portfolio#
6 info lifecycle portfolio#~build: portfolio#
7 verbose lifecycle portfolio#~build: unsafe-perm in lifecycle true
8 verbose lifecycle portfolio#~build: PATH: // Path stuff //
9 verbose lifecycle portfolio#~build: CWD: C:\Users\Simon\Desktop\#Documents\##Projects\Coding\#web\portfolio
10 silly lifecycle portfolio#~build: Args: [ '/d /s /c', 'next build' ]
11 silly lifecycle portfolio#~build: Returned: code: 1 signal: null
12 info lifecycle portfolio#~build: Failed to exec build script
13 verbose stack Error: portfolio# build: `next build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\Simon\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\Simon\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1048:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid portfolio#
15 verbose cwd C:\Users\Simon\Desktop\#Documents\##Projects\Coding\#web\portfolio
16 verbose Windows_NT 10.0.19043
17 verbose argv "C:\\Users\\Simon\\nodejs\\node.exe" "C:\\Users\\Simon\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
18 verbose node v14.16.1
19 verbose npm v6.14.12
20 error code ELIFECYCLE
21 error errno 1
22 error portfolio# build: `next build`
22 error Exit status 1
23 error Failed at the portfolio# build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
.eslintrc.json
{
"extends": "next"
}
**package.json**
{
"name": "portfolio",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
},
"dependencies": {
"#fortawesome/fontawesome-svg-core": "^1.2.36",
"#fortawesome/free-brands-svg-icons": "^5.15.4",
"#fortawesome/free-solid-svg-icons": "^5.15.4",
"#fortawesome/react-fontawesome": "^0.1.16",
"date-fns": "^2.25.0",
"gray-matter": "^4.0.3",
"next": "12.0.3",
"next-mdx-remote": "^3.0.8",
"react": "17.0.2",
"react-dom": "17.0.2",
"sass": "^1.43.4"
},
"devDependencies": {
"eslint": "7.32.0",
"eslint-config-next": "12.0.3"
}
}

Related

Next JS compiling issue mutable globals cannot be exported

Failed to compile.
./assets/images/cross.png
CompileError: AsyncCompile: Wasm decoding failed: mutable globals cannot be exported #+482
> Build error occurred
Error: > Build failed because of webpack errors
at nextBuildSpan.traceAsyncFn (/var/app/kv-v2/node_modules/next/dist/build/index.js:15:924)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! kv-update#1.7.3 build: `next build`
npm ERR! Exit status 1
I am getting this error when trying to npm run build on my ubuntu server it was working fine previously and it is still compiling fine on my localhost windows machine so to be sure it was not due to my code I reverted to the old copy from Github that was working but its still getting the same error when compiling. I did remove the node_modules and reinstalled.
I tried Googling and there were around 10 articles of this none of them were able to fix my issue. Please help me. Thank you. This is the full log file.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using npm#6.14.4
3 info using node#v10.19.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle kv-update#1.7.3~prebuild: kv-update#1.7.3
6 info lifecycle kv-update#1.7.3~build: kv-update#1.7.3
7 verbose lifecycle kv-update#1.7.3~build: unsafe-perm in lifecycle true
8 verbose lifecycle kv-update#1.7.3~build: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/app/kv-v2/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle kv-update#1.7.3~build: CWD: /var/app/kv-v2
10 silly lifecycle kv-update#1.7.3~build: Args: [ '-c', 'next build' ]
11 silly lifecycle kv-update#1.7.3~build: Returned: code: 1 signal: null
12 info lifecycle kv-update#1.7.3~build: Failed to exec build script
13 verbose stack Error: kv-update#1.7.3 build: `next build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid kv-update#1.7.3
15 verbose cwd /var/app/kv-v2
16 verbose Linux 5.4.0-109-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
18 verbose node v10.19.0
19 verbose npm v6.14.4
20 error code ELIFECYCLE
21 error errno 1
22 error kv-update#1.7.3 build: `next build`
22 error Exit status 1
23 error Failed at the kv-update#1.7.3 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
My package.json file
{
"name": "kvr",
"version": "1.7.3",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start -p 4000",
"lint": "next lint"
},
"dependencies": {
"#notbaldrick/react-crossfade-carousel": "^1.0.4",
"babel-plugin-styled-components": "^1.13.1",
"fathom-client": "^3.1.0",
"jsonp": "^0.2.1",
"next": "11.0.1",
"npm": "^6.14.4",
"react": "17.0.2",
"react-device-detect": "^1.17.0",
"react-dom": "17.0.2",
"react-facebook-pixel": "^1.0.4",
"react-img-carousel": "^2.1.1",
"react-responsive-carousel": "^3.2.19",
"react-transition-group": "^4.4.2",
"styled-components": "^5.3.0"
},
"devDependencies": {
"babel-plugin-styled-components": "^1.13.1",
"eslint": "7.30.0",
"eslint-config-next": "11.0.1"
}
}
I did fix it by removing the cross.png file converting it to cross.jpg and updated the code everything it is importing this file. Strange bug It seems.

'npm start' gives an error and does not start the development server

I'm new to node and react and am trying to start a local development server for my react app. To start it I did npm start but this put out an error. The log looks like this:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm#6.14.4
3 info using node#v12.16.3
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle myapp#0.1.0~prestart: myapp#0.1.0
6 info lifecycle myapp#0.1.0~start: myapp#0.1.0
7 verbose lifecycle myapp#0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle myapp#0.1.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;E:\full-stack projects\react tutoral\myapp\node_modules\.bin;C:\Program Files\Git\mingw32\bin;C:\Program Files\Git\usr\bin;C:\Users\User\bin;C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin;C:\Program Files\PostgreSQL\10\bin;C:\Program Files\PostgreSQL\10\libC;C:\Program Files\Git\Python27;C:\Python27\scripts;C:\Users\User\AppData\Local\Programs\Python\Python37-32;C:\Users\User\AppData\Local\Programs\Python\Python37-32\Scripts;C:\Program Files\nodejs;C:\Users\User\AppData\Local\Programs\Microsoft VS Code\bin;C:\Program Files\heroku\bin;C:\Users\User\AppData\Roaming\npm
9 verbose lifecycle myapp#0.1.0~start: CWD: E:\full-stack projects\react tutoral\myapp
10 silly lifecycle myapp#0.1.0~start: Args: [ '/d /s /c', 'react-scripts start' ]
11 silly lifecycle myapp#0.1.0~start: Returned: code: 1 signal: null
12 info lifecycle myapp#0.1.0~start: Failed to exec start script
13 verbose stack Error: myapp#0.1.0 start: `react-scripts start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:310:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:310:20)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid myapp#0.1.0
15 verbose cwd E:\full-stack projects\react tutoral\myapp
16 verbose Windows_NT 6.1.7601
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.16.3
19 verbose npm v6.14.4
20 error code ELIFECYCLE
21 error errno 1
22 error myapp#0.1.0 start: `react-scripts start`
22 error Exit status 1
23 error Failed at the myapp#0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
How do I fix this?
EDIT
Here is the package.json for the app:
{
"name": "myapp",
"version": "0.1.0",
"private": true,
"dependencies": {
"#testing-library/jest-dom": "^4.2.4",
"#testing-library/react": "^9.5.0",
"#testing-library/user-event": "^7.2.1",
"react": "^16.13.1",
"react-dom": "^16.13.1",
"react-scripts": "3.4.1"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": "react-app"
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
EDIT 2
I have tried all the solutions suggested, but it always shows the same errror. Here is how the error is shown in the termianl (bash):
events.js:287
throw er; // Unhandled 'error' event
^
Error: spawn cmd ENOENT
←[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)←[39m
←[90m at onErrorNT (internal/child_process.js:469:16)←[39m
←[90m at processTicksAndRejections (internal/process/task_queues.js:84:21)←[39m
Emitted 'error' event on ChildProcess instance at:
←[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)←[39m
←[90m at onErrorNT (internal/child_process.js:469:16)←[39m
←[90m at processTicksAndRejections (internal/process/task_queues.js:84:21)←[39m {
errno: ←[32m'ENOENT'←[39m,
code: ←[32m'ENOENT'←[39m,
syscall: ←[32m'spawn cmd'←[39m,
path: ←[32m'cmd'←[39m,
spawnargs: [ ←[32m'/s'←[39m, ←[32m'/c'←[39m, ←[32m'start'←[39m, ←[32m'""'←[39m, ←[32m'/b'←[39m, ←[32m'"http://localhost:3000"'←[39m ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! myapp#0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the myapp#0.1.0 start 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! C:\Users\User\AppData\Roaming\npm-cache\_logs\2020-05-07T16_48_16_197Z-debug.log
ignore this line. Stackoverflow requires me to describe the problem in details since most of this is code
Ok so this problem was with the Windows system32 variable. Its actually really easy to solve. Just add the following to the PATH variable:
C:\Windows\System32

Conflict of Node versions

I have on local Windows node v8.12.0 and npm v6.4.1. On the server I have node v11.10.0 and npm v6.7.0.
I replaced project in server with backup on local machine, but when I type npm start I have this error.
sh: 1: react-app-rewired: Permission denied
npm ERR! code ELIFECYCLE
npm ERR! errno 126
npm ERR! manager-polling-app-client#0.1.0 start: `react-app-rewired start`
npm ERR! Exit status 126
npm ERR!
npm ERR! Failed at the manager-polling-app-client#0.1.0 start 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! /root/.npm/_logs/2020-01-14T05_41_00_295Z-debug.log
Is it possible that project does not start on server due to conflict of node version? If yes, should I upgrade node on local or downgrade node on server?
P.S. I think chmod -R 777 will NOT solve problem, because other files on server has the same rights and they start with no problem.
P.P.S. there is my package.json file if it`s needed
{
"name": "manager-polling-app-client",
"version": "0.1.0",
"private": true,
"dependencies": {
"#material-ui/core": "^3.9.3",
"ajv": "^6.9.1",
"ajv-keywords": "^3.4.1",
"antd": "^3.20.0",
"arui-feather": "^12.12.0",
"b64-to-blob": "^1.2.19",
"moment": "^2.22.2",
"pdfmake": "^0.1.53",
"prop-types": "^15.7.2",
"react": "^16.2.0",
"react-awesome-modal": "^2.0.5",
"react-data-export": "^0.5.0",
"react-dom": "^16.2.0",
"react-export-excel": "^0.5.3",
"react-router-dom": "^4.3.1",
"react-scripts": "1.1.1",
"react-select": "^2.4.2",
"xlsx": "^0.14.4"
},
"scripts": {
"start": "react-app-rewired start",
"build": "react-app-rewired build",
"test": "react-app-rewired test --env=jsdom",
"eject": "react-scripts eject"
},
"devDependencies": {
"babel-plugin-import": "^1.11.0",
"react-app-rewire-less": "^2.1.3",
"react-app-rewired": "^1.6.2"
}
}
P.P.P.S. Log file
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using npm#6.7.0
3 info using node#v11.10.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle manager-polling-app-client#0.1.0~prestart: manager-polling-app- client#0.1.0
6 info lifecycle manager-polling-app-client#0.1.0~start: manager-polling-app-cli ent#0.1.0
7 verbose lifecycle manager-polling-app-client#0.1.0~start: unsafe-perm in lifec ycle true
8 verbose lifecycle manager-polling-app-client#0.1.0~start: PATH: /usr/local/lib /node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/root/mybpm/manager-po lling-app-client/node_modules/.bin:/usr/lib/jvm/java-8-openjdk-amd64/bin:/usr/lo cal/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/game s:/snap/bin
9 verbose lifecycle manager-polling-app-client#0.1.0~start: CWD: /root/mybpm/man ager-polling-app-client
10 silly lifecycle manager-polling-app-client#0.1.0~start: Args: [ '-c', 'react- app-rewired start' ]
11 silly lifecycle manager-polling-app-client#0.1.0~start: Returned: code: 126 signal: null
12 info lifecycle manager-polling-app-client#0.1.0~start: Failed to exec start s cript
13 verbose stack Error: manager-polling-app-client#0.1.0 start: `react-app-rewir ed start`
13 verbose stack Exit status 126
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/np m/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:197:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/np m/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:197:13)
13 verbose stack at maybeClose (internal/child_process.js:984:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_proc ess.js:265:5)
14 verbose pkgid manager-polling-app-client#0.1.0
15 verbose cwd /root/mybpm/manager-polling-app-client
16 verbose Linux 4.4.0-135-generic
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
18 verbose node v11.10.0
19 verbose npm v6.7.0
20 error code ELIFECYCLE
21 error errno 126
22 error manager-polling-app-client#0.1.0 start: `react-app-rewired start`
22 error Exit status 126
23 error Failed at the manager-polling-app-client#0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional log

React.js create-react-app Npm Run Build - Failed

In my React create-react-app projects npm start is working fine, but the 'build' script fails almost immediately.
The error says failed to compile - 'EISDIR: illegal operation on a directory, read'
I've tried completely uninstalling and reinstalling node & npm using nvm.
I've tried creating a new create-react-app project without editing any of preloaded code, and build still fails.
terminal error message:
Creating an optimized production build...
Failed to compile.
EISDIR: illegal operation on a directory, read
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! personal-website#0.1.0 build: react-scripts build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the personal-website#0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Debug log:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/Users/Stew/.nvm/versions/node/v12.7.0/bin/node',
1 verbose cli '/Users/Stew/.nvm/versions/node/v12.7.0/bin/npm',
1 verbose cli 'run',
1 verbose cli 'build'
1 verbose cli ]
2 info using npm#6.10.2
3 info using node#v12.7.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle personal-website#0.1.0~prebuild: personal-website#0.1.0
6 info lifecycle personal-website#0.1.0~build: personal-website#0.1.0
7 verbose lifecycle personal-website#0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle personal-website#0.1.0~build: PATH: /Users/Stew/.nvm/versions/node/v12.7.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/Stew/Desktop/personal-website/node_modules/.bin:/Users/Stew/.nvm/versions/node/v12.7.0/bin:/usr/bin:/usr/sbin:/bin:/sbin
9 verbose lifecycle personal-website#0.1.0~build: CWD: /Users/Stew/Desktop/personal-website
10 silly lifecycle personal-website#0.1.0~build: Args: [ '-c', 'react-scripts build' ]
11 silly lifecycle personal-website#0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle personal-website#0.1.0~build: Failed to exec build script
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/Users/Stew/.nvm/versions/node/v12.7.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:326:16)
13 verbose stack at EventEmitter.emit (events.js:203:13)
13 verbose stack at ChildProcess.<anonymous> (/Users/Stew/.nvm/versions/node/v12.7.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:203:13)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid personal-website#0.1.0
15 verbose cwd /Users/Stew/Desktop/personal-website
16 verbose Darwin 18.6.0
17 verbose argv "/Users/Stew/.nvm/versions/node/v12.7.0/bin/node" "/Users/Stew/.nvm/versions/node/v12.7.0/bin/npm" "run" "build"
18 verbose node v12.7.0
19 verbose npm v6.10.2
20 error code ELIFECYCLE
21 error errno 1
22 error personal-website#0.1.0 build: `react-scripts build`
22 error Exit status 1
23 error Failed at the personal-website#0.1.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
package.json
{
"name": "personal-website",
"version": "0.1.0",
"private": true,
"dependencies": {
"react": "^16.8.6",
"react-dom": "^16.8.6",
"react-scripts": "3.0.1"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": "react-app"
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
I expect the react project to successfully compile the production build script, but instead it creates the build repository and immediate fails after creating a manifest.json and gives the error message listed above.

nodejs webpack server not starting

I am new to NodeJs and trying to setup react app. Getting following error on the console while starting the server.
Not able to start the server, have tried several options.
c:\Users\vaibhav\Desktop\node>npm start
> test#1.0.0 start c:\Users\vaibhav\Desktop\node
> webpack-dev-server --hot
x ?wds?: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration.module has an unknown property 'loaders'. These properties are valid:
object { exprContextCritical?, exprContextRecursive?, exprContextRegExp?, exprContextRequest?, noParse?, rules?, defaultRules?, unknownContextCritical?, unknownContextRecursive?, unknownContextRegExp?, unknownContextRequest?, unsafeCache?, wrappedContextCritical?, wrappedContextRecursive?, wrappedContextRegExp?, strictExportPresence?, strictThisContextOnImports? }
-> Options affecting the normal modules (`NormalModuleFactory`).
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! test#1.0.0 start: `webpack-dev-server --hot`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the test#1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional log
ging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\vaibhav\AppData\Roaming\npm-cache\_logs\2018-09-06T17_00_03
_303Z-debug.log
The log file shows the following error:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'start' ]
2 info using npm#5.6.0
3 info using node#v8.11.4
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle test#1.0.0~prestart: test#1.0.0
6 info lifecycle test#1.0.0~start: test#1.0.0
7 verbose lifecycle test#1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle test#1.0.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;c:\Users\vaibhav\Desktop\node\node_modules\.bin;C:\Windows;C:\Windows\system32;C:\Windows\system32\wbem;C:\ProgramData\Oracle\Java\javapath;C:\app\vaibhav\product\11.2.0\client_1\bin;C:\Program Files (x86)\Attachmate\E!E2K\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Attachmate\Reflection\;C:\Users\vaibhav\AppData\Local\Programs\Python\Python36;C:\Users\vaibhav\AppData\Local\Programs\Python\Python36\Scripts;C:\Strawberry\c\bin;C:\Strawberry\perl\site\bin;C:\Strawberry\perl\bin;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\1E\NomadBranch\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseSVN\bin;C:\Users\vaibhav\Documents\softwares\apache-maven-3.3.3\bin;C:\Program Files (x86)\GNU\GnuPG;C:\Program Files (x86)\Enterprise Vault\EVClient\;C:\Program Files (x86)\Java\jre1.8.0_152\bin;C:\Program Files (x86)\WebEx\Productivity Tools;C:\Program Files (x86)\CheckPoint\Endpoint Security\Endpoint Common\bin;C:\Program Files\nodejs\;C:\Users\vaibhav\AppData\Local\GitHubDesktop\bin;C:\Program Files\Microsoft VS Code\bin;C:\Users\vaibhav\AppData\Roaming\npm
9 verbose lifecycle test#1.0.0~start: CWD: c:\Users\vaibhav\Desktop\node
10 silly lifecycle test#1.0.0~start: Args: [ '/d /s /c', 'webpack-dev-server --hot' ]
11 silly lifecycle test#1.0.0~start: Returned: code: 1 signal: null
12 info lifecycle test#1.0.0~start: Failed to exec start script
13 verbose stack Error: test#1.0.0 start: `webpack-dev-server --hot`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\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> (C:\Program Files\nodejs\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 test#1.0.0
15 verbose cwd c:\Users\vaibhav\Desktop\node
16 verbose Windows_NT 6.1.7601
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "start"
18 verbose node v8.11.4
19 verbose npm v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error test#1.0.0 start: `webpack-dev-server --hot`
22 error Exit status 1
23 error Failed at the test#1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
My package.json looks like the following:
{
"name": "test",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"start": "webpack-dev-server --hot"
},
"author": "",
"license": "ISC",
"dependencies": {
"babel-core": "^6.26.3",
"babel-loader": "^8.0.2",
"babel-preset-es2015": "^6.24.1",
"babel-preset-react": "^6.24.1",
"react": "^16.4.2",
"react-dom": "^16.4.2",
"webpack": "^4.17.2",
"webpack-dev-server": "^3.1.7"
},
"devDependencies": {
"webpack-cli": "^3.1.0"
}
}
Please let me know in case you require more details. I will provide that in comments.
The answer is in your question:
wds?: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration.module has an unknown property 'loaders'. These properties are valid: object { exprContextCritical?, exprContextRecursive?, exprContextRegExp?, exprContextRequest?, noParse?, rules?, defaultRules?, unknownContextCritical?, unknownContextRecursive?, unknownContextRegExp?, unknownContextRequest?, unsafeCache?, wrappedContextCritical?, wrappedContextRecursive?, wrappedContextRegExp?, strictExportPresence?, strictThisContextOnImports? }
In your config, instead of module.loaders, it has to be module.rules.

Resources