-
Notifications
You must be signed in to change notification settings - Fork 25
Description
Prerequisites
Please answer the following questions for yourself before submitting an issue.
- [yes ] I am running the latest version
- [yes ] I checked the documentation and found no answer
- [yes ] I checked to make sure that this issue has not already been filed
- [ yes] I'm reporting the issue to the correct repository (for multi-repository projects)
Expected Behavior
No errors after npm install.
Current Behavior
npm install give npm ERR! ERESOLVE unable to resolve dependency tree
Failure Information (for bugs)
Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
- Download the source code
- unpack the zip folder
- npm install -g expo-cli
- npm install
- Erros occur
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
- Device: Acer Nitro 5
- Operating System: Windows 10
- Browser and Version: Google Chrome Version 89.0.4389.82
Failure Logs
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR! react@"16.13.1" from the root project
npm ERR! peer react@"16.13.1" from [email protected]
npm ERR! node_modules/jest-expo
npm ERR! dev jest-expo@"^40.0.0" from the root project
npm ERR! 2 more (react-native, react-native-web)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"17.0.1" from [email protected]
npm ERR! node_modules/react-dom
npm ERR! peer react-dom@">=16.5.1" from [email protected]
npm ERR! node_modules/react-native-web
npm ERR! peer react-native-web@"~0.13.7" from [email protected]
npm ERR! node_modules/jest-expo
npm ERR! dev jest-expo@"^40.0.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.