infinitered / infinitered/reactotron
Dependency Issue with Latest version
- Dominant language
- TypeScript
- Stars
- 15.6k
- Forks
- 972
- PR merge metrics
- No merged PRs in 30d
Description
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: *******
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR! react@"17.0.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.2.1 || 16.0.0-alpha.6 || 16.0.0-alpha.12 || 16.0.0-beta.5 || ^16.0.0" from reactotron-react-native@5.0.0
npm ERR! node_modules/reactotron-react-native
npm ERR! dev reactotron-react-native@"*" 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.
npm ERR!
npm ERR! See /Users/**********/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/**********/.npm/_logs/2021-07-05T07_42_49_083Z-debug.log
Contributor guide
Research direction
Start by reproducing the npm dependency-resolution error using React 17.0.1 and reactotron-react-native@5.0.0 from the issue. Check the package compatibility and dependency declarations; done means installation resolves without relying on --force or --legacy-peer-deps, but the issue does not identify a target file or preferred version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, react, react-native
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100