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

Question

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": "9.0.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:

Answer 1

create .env file in your project file and add the following statement

SKIP_PREFLIGHT_CHECK=true

Save the file

Remove node_modules, yarn.lock, package.lock

Then reinstall node_modules with

npm install

This should work

Answer 2

I had the same problem and do all the suggested steps but the problem still, so, my error is that i have a reactApp inside other Javascript App i had this structure.

--MyProjects
----NodeJsApp
----node_modules of NodeJsApp
----package.json of NodeJsApp
----ReactApp
------node_modules of ReactApp
------package.json of ReactApp

The problem solved to me deleting my ReactApp node_modules directory, then i do a reestructure of my directories because i have a disaster.

--MyProjects
----NewDirectory (inside all about NodeJsApp)
------node_modules of NodeJsApp
------package.json of NodeJsApp
----ReactApp
------package.json of ReactApp

After that i do :

npm install

and then npm start and my problem has fixed, i think that the problem is that the parent directory cant have a javascript /nodeJs/ project or something that have node_modules .

Answer 3

Part of the output you provided says:

Check if C:\Users\chawki\node_modules\babel-eslint is outside your project directory. For example, you might have accidentally installed something in your home folder.

Browse to C:\Users\chawki\node_modules\ and delete the babel-eslint folder, or simply delete C:\Users\chawki\node_modules.

Answer 4

I just deleted the node_modules folder (for me it was C:\user\[yourUserName]\node_modules\) and re-installed it.

Answer 5

Here What i did...

1. C:\user\[yourUserName]\node_modules\babel-eslint and delete the file
2. C:\user\[yourUserName]\node_modules\eslint and delete the file

Answer 6

Delete your eslint and babel-eslint file from your node modules on your computer e.g. -C:\Users\vishnu\node_modules -delete eslint and babel-eslint file.

In your project:

yarn remove eslint
yarn add --dev [email protected]

yarn remove babel-eslint
yarn add --dev [email protected]

Answer 7

in package.json

resolutions:{
    "babel-eslint": "9.0.0"
}

if you reinstall your all dependencies, you will be forcing "babel-eslint" to be version "9.0.0". if you start your app, you will have no issue.

Answer 8

My problem was I installed webpack as a global package... after i deleted webpact and run npm install, the problem was gone

Answer 9

Make sure you don't have a global webpack package or somewhere higher up the directory structure. In my case, I had it globally installed. Deleting and then running npm install and then npm start worked perfectly.

Answer 10

Run npm ls babel-eslint and see which dependencies are using it or installing another version. Try updating those libraries.

It worked for me.

Answer 11

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 "webpack" 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 /home/shayon/node_modules/webpack is outside your project directory. For example, you might have accidentally installed something in your home folder.

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

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.