Failed to exec start script

Is this a bug report?

Yes

Did you try recovering your dependencies?

(Write your answer here.) yarn --version 1.15.2

Which terms did you search for in User Guide?

(Write your answer here if relevant.) Failed to exec start script react-scripts

Environment

(paste the output of the command here) System: OS: Linux 5.0 Antergos Linux CPU: (8) x64 Intel® Core™ i7-6700HQ CPU @ 2.60GHz Binaries: Node: 11.14.0 - /usr/bin/node Yarn: 1.15.2 - /usr/bin/yarn npm: 6.9.0 - /usr/bin/npm Browsers: Chrome: Not Found Firefox: 66.0.3 npmPackages: react: ^16.8.6 => 16.8.6 react-dom: ^16.8.6 => 16.8.6 react-scripts: 3.0.0 => 3.0.0 npmGlobalPackages: create-react-app: Not Found

Steps to Reproduce

(Write your steps here:)

1. I have tried to use (again) the project starter for React (react-create-app) and after following the first 3steps of the official documentation the terminal throws an error when I try to start the project

Expected Behavior

(Write what you thought would happen.) Compiled successfully!

You can now view project in the browser.

Local: http://localhost:3000/ On Your Network: http://10.1.0.116:3000/

Note that the development build is not optimized. To create a production build, use yarn build.

Actual Behavior

(Write what happened. Please add screenshots!) Starting the development server…

events.js:170 throw er; // Unhandled ‘error’ event ^

Error: spawn /usr/bin/chromium ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:247:19) at onErrorNT (internal/child_process.js:429:16) at processTicksAndRejections (internal/process/task_queues.js:81:17) Emitted ‘error’ event at: at Process.ChildProcess._handle.onexit (internal/child_process.js:253:12) at onErrorNT (internal/child_process.js:429:16) at processTicksAndRejections (internal/process/task_queues.js:81:17) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! project@0.1.0 start: react-scripts start npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the project@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! /home/florin/.npm/_logs/2019-05-02T13_52_24_047Z-debug.log

And the log is

0 info it worked if it ends with ok 1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ] 2 info using npm@6.9.0 3 info using node@v11.14.0 4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ] 5 info lifecycle project@0.1.0~prestart: project@0.1.0 6 info lifecycle project@0.1.0~start: project@0.1.0 7 verbose lifecycle project@0.1.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle project@0.1.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/florin/WebstormProjects/project/node_modules/.bin:/home/florin/.local/bin:/home/florin/bin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl 9 verbose lifecycle project@0.1.0~start: CWD: /home/florin/WebstormProjects/project 10 silly lifecycle project@0.1.0~start: Args: [ ‘-c’, ‘react-scripts start’ ] 11 silly lifecycle project@0.1.0~start: Returned: code: 1 signal: null 12 info lifecycle project@0.1.0~start: Failed to exec start script 13 verbose stack Error: project@0.1.0 start: react-scripts start 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16) 13 verbose stack at EventEmitter.emit (events.js:193:13) 13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:193:13) 13 verbose stack at maybeClose (internal/child_process.js:999:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:266:5) 14 verbose pkgid project@0.1.0 15 verbose cwd /home/florin/WebstormProjects/project 16 verbose Linux 5.0.10-arch1-1-ARCH 17 verbose argv “/usr/bin/node” “/usr/bin/npm” “start” 18 verbose node v11.14.0 19 verbose npm v6.9.0 20 error code ELIFECYCLE 21 error errno 1 22 error project@0.1.0 start: react-scripts start 22 error Exit status 1 23 error Failed at the project@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 ]

END

Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.) Since i haven’t added nothing extra to the react starter project I can’t share you a link, is just the starting project that it has issues on my machine. It is working if I change the version of the “react-scripts” from 3.0.0 - to 2.1.8

[DrKhyz]

I’ve found another solution more easy. In your package.json, just add BROWSER=none before react-scripts start. THis will not launch the browser, and you will not have errors

BROWSER=none react-scripts start

[florin1000]

I think I found the issue. 1)in the file mentioned above by @ianschmitz the getBrowserEnv function is reading the environment variable BROWSER and if, like in my case is /usr/bin/chromium and there is no such binary in the specified path it doesn’t have what to open.

My Solution: set your BROWSER env variable to the right binary, in my case is

/usr/bin/google-chrome-stable with export BROWSER=/usr/bin/google-chrome-stable

or you can modify the file @ianschmitz getBrowserEnv function with the binary you desire, set the value const: const value = "/usr/bin/your-binary-here"

I am wondering if this is a react-create-app bug for not cathcing this special case or an antergros error for not setting the env variable at installing google-chrome-stable!