from node-10-16 lts, impossible to run nm start after npx create-react-app my_app [closed]

[jerome-diver]

Describe the bug

from node-10-16 lts, impossible to run nm start after npx create-react-app my_app
errors are:
events.js:174
throw er; // Unhandled 'error' event
^

Error: spawn /usr/bin/palemoon ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! memory@0.1.0 start: react-scripts start
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the memory@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/jerome/.npm/_logs/2019-07-28T06_52_10_841Z-debug.log

after installed package-lock.json, as suggested above, the server doesn't start and no error message....
yarn.lock installed but node_modules can not with many error again:
npm ERR! code ETARGET
npm ERR! notarget No matching version found for undefined@node_modules
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/jerome/.npm/_logs/2019-07-28T06_54_34_517Z-debug.log

npm version is 6.10.2

I don't want to remove my official repos packages (it is a very bad practice) ad i hope it is possible to just use react with lts node application,if not, it housld be impossible ofr me to learn and use react due to miss-respect version lts concept and unmaintainable applications from this crucial point.

Environment

npx create-react-app --info

Environment Info:

System:
OS: Linux 5.2 Arch Linux
CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
Binaries:
Node: 10.16.0 - /usr/bin/node
Yarn: Not Found
npm: 6.10.2 - /usr/bin/npm
Browsers:
Chrome: Not Found
Firefox: 68.0.1
npmPackages:
react: ^16.8.6 => 16.8.6
react-dom: ^16.8.6 => 16.8.6
react-scripts: 3.0.1 => 3.0.1
npmGlobalPackages:
create-react-app: 3.0.1

Steps to reproduce

1. npm install -g create-react-app
2. npx create-react-app my_app
3. cd my_app
4. npm start

Expected behavior

server should run with information about server access url

Actual behavior

[mrmckeb]

Hi @jerome-diver,

We definitely support the Node LTS range.

I don't want to remove my official repos packages (it is a very bad practice) ad i hope it is possible to just use react with lts node application
If you mean that you haven't tried deleting your node_modules folder and reinstalling, I don't think we can help a lot at this stage - as this is a common fix for the issue you've identified.

Please try that and let me know how it goes.

rm -rf node_modules yarn.lock && yarn

[jerome-diver]

hi @mrmckeb and thank you for your help. I do try what you tell me, but unfortunately, i get an error:

After read carefully the error message, i understand that my BROWSER environment variable ask for palemoon web-browser (i removed it). So, export BROWSER environment variable to existing one (firefox) do resolve the problem.

what's happened

And then I can see that the default application when start from npm doesn't just start, but want absolutely start the default system web-browser and doesn't handle an except error in case of this one doesn't exist (i think it is not a bug really, but something can be done to let users free to open the web-browser they want and look at indicated url, same it was before if i well understand how-to pages around the www)

what can be better maybe

The best way for all situation maybe can be to try to open a web-browser and if exception (what ever to do next, it should have one exception to catch) on that, just indicate the url to look at.

it was a problem, not a real bug

Thank you very much again for your help who resolved my problem after i do install yarn and follow your requirement.

[aman-kumar-jh]

upgrade the npm version to 10.2.3 should solve the problem and after upgrading npm download the repository again