Last versions (from 1.0.0) cannot start and show the following error:
webpack.validateSchema is not a function
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start-js: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start-js script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
And the following is in the log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'start-js' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart-js', 'start-js', 'poststart-js' ]
5 info lifecycle [email protected]~prestart-js: [email protected]
6 silly lifecycle [email protected]~prestart-js: no script for prestart-js, continuing
7 info lifecycle [email protected]~start-js: [email protected]
8 verbose lifecycle [email protected]~start-js: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start-js: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/user/src/project/frontend/node_modules/.bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
10 verbose lifecycle [email protected]~start-js: CWD: /home/user/src/project/frontend
11 silly lifecycle [email protected]~start-js: Args: [ '-c', 'react-scripts start' ]
12 silly lifecycle [email protected]~start-js: Returned: code: 1 signal: null
13 info lifecycle [email protected]~start-js: Failed to exec start-js script
14 verbose stack Error: [email protected] start-js: `react-scripts start`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/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:194:7)
14 verbose stack at ChildProcess.<anonymous> (/usr/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:194:7)
14 verbose stack at maybeClose (internal/child_process.js:899:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/user/src/project/frontend
17 verbose Linux 4.10.13-1-ARCH
18 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "start-js"
19 verbose node v7.10.0
20 verbose npm v4.6.1
21 error code ELIFECYCLE
22 error errno 1
23 error [email protected] start-js: `react-scripts start`
23 error Exit status 1
24 error Failed at the [email protected] start-js script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
Everything works like in the previous version (0.9.5).
It doesn't work. rm -rf node_modules && npm install doesn't help. Rollback to the version 0.9.5 helps.
Haven't tried to rollback webpack-dev-server to the first version.
Run these commands in the project folder and fill in their results:
npm ls react-scripts (if you haven’t ejected):node -v:npm -v:Then, specify:
Please provide a full project reproducing this.
Or at least your package.json.
+1
Here is my package.json as I am receiving the same error.
{
"name": "frontend",
"version": "0.1.0",
"private": true,
"dependencies": {
"react": "^15.5.4",
"react-dom": "^15.5.4"
},
"devDependencies": {
"react-scripts": "1.0.7"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test --env=jsdom",
"eject": "react-scripts eject"
}
}
Can you provide a project reliably reproducing this? Have you tried to use a different npm version (or Yarn)? Have you tried npm cache clear before running npm install?
I was seeing the same issue and the problem was #2352. Storybook is holding on to an old version of webpack and that's the one that create-react-app attempts to use. I think there was a note about that in one of the releases but I forgot to remove the dependency before I tried upgrading.
react-scripts v1.0.10, node v8.2.1, npm v5.3.0 - still the same. Even after npm cache --force clear. With Yarn it works fine.
If you keep experiencing it please file a new issue with all information requested in the issue template, and we’ll try to help!
Most helpful comment
+1
Here is my
package.jsonas I am receiving the same error.