Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Getting an error trying to start React right after (There might be a problem with the project dependency tree....)

I have created React App from npx create-react-app. And, I tried to cd and start the app and it shows this error. I tried with yarn and reinstalling node as well. I am super lost since it was wooooorking like 30 minutes ago as well. The only thing I did was npm i -g npm to update npm and since then it is not working.

We suggest that you begin by typing:

  cd giact
  yarn start

Happy hacking!
gi@Gis-Macbook-Pro study % cd giact
gi@Gis-Macbook-Pro giact % npm start

> [email protected] start /Users/gi/Desktop/Study/giact
> react-scripts start


There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.

The react-scripts package provided by Create React App requires a dependency:

  "babel-eslint": "10.1.0"

Don't try to install it manually: your package manager does it automatically.
However, a different version of babel-eslint was detected higher up in the tree:

  /Users/gi/node_modules/babel-eslint (version: 9.0.0) 

Manually installing incompatible versions is known to cause hard-to-debug issues.

If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.

To fix the dependency tree, try following the steps below in the exact order:

  1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
  2. Delete node_modules in your project folder.
  3. Remove "babel-eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
  4. Run npm install or yarn, depending on the package manager you use.

In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:

  5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
     This may help because npm has known issues with package hoisting which may get resolved in future versions.

  6. Check if /Users/gi/node_modules/babel-eslint is outside your project directory.
     For example, you might have accidentally installed something in your home folder.

  7. Try running npm ls babel-eslint in your project folder.
     This will tell you which other package (apart from the expected react-scripts) installed babel-eslint.

If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.

P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `react-scripts start`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] 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!     /Users/gi/.npm/_logs/2020-04-19T18_13_36_022Z-debug.log
like image 379
chichi Avatar asked Apr 19 '20 18:04

chichi


People also ask

How do I fix create react error?

Use npx to solve the error "create-react-app: command not found", e.g. npx create-react-app my-app or install the package globally by running npm install -g create-react-app to be able to use the command without the npx prefix. The fastest way to solve the error is to use the npx command.

How do I resolve npm start error?

To solve the Missing script: "start" error, make sure to add a start command to the scripts object in your package. json file and open your shell or IDE in the root directory of your project before running the npm start command.


4 Answers

1) The react-scripts package provided by Create React App requires a dependency:

"babel-eslint": "10.1.0", "eslint": "^6.8.0"

Use command: npm install [email protected] babel-eslint@10 --save-dev

like image 149
kwny Avatar answered Oct 23 '22 21:10

kwny


/Users/gi go to this and type npm i [email protected] It would solve your problem. Its worked for me

like image 30
Afroz Atoz Avatar answered Oct 23 '22 23:10

Afroz Atoz


My problem was solved by deleting node_modules that was in my "C:\Users" folder.

like image 21
Gullian Van Der Walt Avatar answered Oct 23 '22 21:10

Gullian Van Der Walt


A quick fix is creating a file named .env in the project folder with the following content SKIP_PREFLIGHT_CHECK=true

I couldn't get anything else to work, npm, yarn, deleting lock, deleting node_modules, etc. This is just happening in my linux mint environment, not on windows or ubuntu.

like image 45
Luis Puente Avatar answered Oct 23 '22 22:10

Luis Puente