yarn start throws error message after installing eslint-config-react-app
See original GitHub issueDescribe the bug
After running
npx create-react-app my-app
switching to my-app directory and running
yarn start
This works fine. Then I run the following on the command line (Please see for more information about this specific command here: https://github.com/upleveled/eslint-config-upleveled
npx install-peerdeps --yarn --dev @upleveled/eslint-config-upleveled
and after that
yarn start
again. Still works fine. But as soon as I run
npx install-peerdeps --yarn --dev eslint-config-react-app
or as an alternative
npx install-peerdeps --yarn --dev --only-peers eslint-config-react-app
If I try
yarn start
now it gives me the following error message:
$ yarn start
yarn run v1.22.5
$ 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:
C:\Coding\workspace\my-custom-app-name\node_modules\babel-eslint (version: 10.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 C:\Coding\workspace\my-custom-app-name\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!
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
User@User-PC MINGW64 /c/Coding/workspace/my-custom-app-name (main)
Did you try recovering your dependencies?
Yes, I did it with yarn as described.
(Write your answer here.)
Which terms did you search for in User Guide?
The react-scripts package provided by Create React App requires a dependency:
“babel-eslint”: “^10.1.0”
(Write your answer here if relevant.)
Environment
System: OS: Windows 10 10.0.19041 CPU: (8) x64 Intel® Core™ i7-2720QM CPU @ 2.20GHz Binaries: Node: 15.4.0 - C:\Program Files\nodejs\node.EXE Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD npm: 7.1.1 - C:\Program Files\nodejs\npm.CMD Browsers: Chrome: 88.0.4324.104 Edge: Spartan (44.19041.423.0), Chromium (88.0.705.50) Internet Explorer: 11.0.19041.1 npmPackages: react: ^17.0.1 => 17.0.1 react-dom: ^17.0.1 => 17.0.1 react-scripts: 4.0.1 => 4.0.1 npmGlobalPackages: create-react-app: Not Found
Steps to reproduce
please see section ### Describe the bug
Expected behavior
yarn start
Starts the react app.
Actual behavior
please see section ### Describe the bug
Reproducible demo
No changes in my project. Just created it as described in ### Describe the bug
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:7
Top GitHub Comments
I tried it on my Windows pc and it threw the error but not for my macOS laptop
@apollo42 thanks! Maybe we can fix the issue over in nathanhleung/install-peerdeps#127 then.
@uebriges you can probably close this now.