-
Notifications
You must be signed in to change notification settings - Fork 107
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
yarn add react-native-razorpay updates my project's yarn.lock #144
Comments
@GaudamThiyagarajan move the dependencies in the package.json of react-native-razorpay to devDependencies (yet to try out but according to my research it is the cause of this issue).Have a look at this link and make sure you update your react-native and react version in your main package.json |
Updating from 0.55 to 0.57 is not a simple task. We have to look upgrade related to babel@7 and other dependency changes is there a simpler way to support 0.55. Why does [email protected] also adds additional reactnative linking to 0.57 when razorpay's package.json says (@>=0.55) |
I forked your repo and downgraded the react to 0.55.4 and react to 16.3.1 and used that. This package doesn't need react native 0.57.x |
@GaudamThiyagarajan the fact behind this is react-native on Xcode 10 is unstable , they are still making fixes for it , it is highly recommended that you use the latest version of react-native as it contains a lot of Xcode 10 fixes. |
Since we are working with only react-native for android would it still be a problem? |
@GaudamThiyagarajan I don't think so. |
Before razorpay installation
react [email protected] and [email protected] and [email protected]
After razorpay sdk installation in yarn.lock we get two react-native of different versions
on react-native-razorpay/master we are getting two versions
[email protected] and [email protected]
on react-native-razorpay/2.0.10 we are getting two versions
[email protected] and react-native@>=0.55.0
Our own metro bundler and babel are getting updated to razorpay's package.json
How to avoid these unnecessary updates
The text was updated successfully, but these errors were encountered: