-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation Error: unable to resolve dependency tree #153
Comments
i don't think it has anything to do with this lib.
it seems react-native require 16.9 while another lib require 16.12
Usually we should meet the requirements of react-native first and try to force other libs to accept.
…---Original---
From: ***@***.***>
Date: Wed, Feb 16, 2022 12:30 PM
To: ***@***.***>;
Cc: ***@***.***>;
Subject: [magicismight/react-native-root-toast] Installation Error: unable toresolve dependency tree (Issue #153)
Hi,
I failed to install the package onto my project. is there any missing dependencies?
"react": "16.12.0", "react-native": "0.61.4",
and here's the installation error:
npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: ***@***.*** npm ERR! Found: ***@***.*** npm ERR! node_modules/react npm ERR! react@"16.12.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"16.9.0" from ***@***.*** npm ERR! node_modules/react-native npm ERR! react-native@"0.61.4" from the root project npm ERR! peer react-native@">=0.47.0" from ***@***.*** npm ERR! node_modules/react-native-root-toast npm ERR! react-native-root-toast@"*" from the root project
thanks
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I failed to install the package onto my project. is there any missing dependencies?
and here's the installation error:
thanks
The text was updated successfully, but these errors were encountered: