I have a problem on my OS X(Version 10.13.6)
See original GitHub issueIs this a bug report?
probably, yes
Did you try recovering your dependencies?
What I tried was just to delete node_modules and reinstall it again, but it didn’t work. I didn’t use yarn to fix it. If I run the project created by the new create-react-app on my docker container, it works properly with just normal command like “npm start.” However, when it comes to the terminal of my OS X, it doesn’t work at all unless I change “react-scripts” back to 1.1.5 from 2.0.3 in the package.json. It means that if react-scripts is 1.1.5, it can run on OS X like before.
Which terms did you search for in User Guide?
Environment
OS X(Version 10.13.6)
node -v v10.11.0
npm -v 6.4.1
create-react-app -V 2.0.2
Steps to Reproduce
npm init react-app my-app cd my-app/ npm start
Expected Behavior
It should open browser.
Actual Behavior
10 silly lifecycle my-app@0.1.0~start: Args: [ ‘-c’, ‘react-scripts start’ ]
11 silly lifecycle my-app@0.1.0~start: Returned: code: 1 signal: null
12 info lifecycle my-app@0.1.0~start: Failed to exec start script
13 verbose stack Error: my-app@0.1.0 start: react-scripts start
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/Users/usr/.nodebrew/node/v10.11.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:182:13)
13 verbose stack at ChildProcess.<anonymous> (/Users/usr/.nodebrew/node/v10.11.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:182:13)
13 verbose stack at maybeClose (internal/child_process.js:962:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
20 error code ELIFECYCLE
21 error errno 1
22 error my-app@0.1.0 start: react-scripts start
22 error Exit status 1
23 error Failed at the my-app@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 ]
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (2 by maintainers)
Top GitHub Comments
I made it work. Thank you so much. @Timer
Looks like you have a dangling
webpack
dependency up in your tree. Please go up each folder, removingnode_modules
.