question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Description

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! project@0.1.0 start-js: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the project@0.1.0 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 npm@4.6.1
3 info using node@v7.10.0
4 verbose run-script [ 'prestart-js', 'start-js', 'poststart-js' ]
5 info lifecycle project@0.1.0~prestart-js: project@0.1.0
6 silly lifecycle project@0.1.0~prestart-js: no script for prestart-js, continuing
7 info lifecycle project@0.1.0~start-js: project@0.1.0
8 verbose lifecycle project@0.1.0~start-js: unsafe-perm in lifecycle true
9 verbose lifecycle project@0.1.0~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 project@0.1.0~start-js: CWD: /home/user/src/project/frontend
11 silly lifecycle project@0.1.0~start-js: Args: [ '-c', 'react-scripts start' ]
12 silly lifecycle project@0.1.0~start-js: Returned: code: 1  signal: null
13 info lifecycle project@0.1.0~start-js: Failed to exec start-js script
14 verbose stack Error: project@0.1.0 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 project@0.1.0
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 project@0.1.0 start-js: `react-scripts start`
23 error Exit status 1
24 error Failed at the project@0.1.0 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 ]

Expected behavior

Everything works like in the previous version (0.9.5).

Actual behavior

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.

Environment

Run these commands in the project folder and fill in their results:

  1. npm ls react-scripts (if you haven’t ejected): project@0.1.0 /home/user/src/project/frontend └── react-scripts@1.0.6
  2. node -v: v7.10.0
  3. npm -v: 4.6.1

Then, specify:

  1. Operating system: Linux

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
Ryanb58commented, May 27, 2017

+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"
  }
}
0reactions
gaearoncommented, Jul 24, 2017

If you keep experiencing it please file a new issue with all information requested in the issue template, and we’ll try to help!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshoot startup errors on Xbox
You can reset your console from the Xbox Startup Troubleshooter. From the Something went wrong screen, use the D-pad and A button on...
Read more >
If your Mac doesn't start up all the way - Apple Support
If your Mac doesn't start up all the way or needs you to do something during startup, it might stop at one of...
Read more >
How to fix Xbox One startup errors or E error codes
Launch Xbox Startup Troubleshooter · Turn off your console, and remove the cords. · Wait for a minute, and then plug the power...
Read more >
How to Fix Errors Seen During the Computer Startup Process
An error message during startup is an indication of a specific problem, so it's important to troubleshoot the specific issue the message is ......
Read more >
Startup error - Microsoft Community
If resetting your console does not correct your startup error, you can use the Xbox Startup Troubleshooter to completely restore your console to ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found