Replies: 3 comments 1 reply
-
|
Thanks for the feedback! You're correct - Nitro Modules is designed to be backwards compatible. Current ConfigurationLooking at our {
"peerDependencies": {
"react-native-nitro-modules": "^0.31.1"
}
}The Why This Works
If you're experiencing version conflicts, make sure your project's lockfile isn't forcing an older version. You can try: # Yarn
yarn up react-native-nitro-modules
# npm
npm update react-native-nitro-modules |
Beta Was this translation helpful? Give feedback.
-
|
^0.31.1 this makes it not compatible with 0.32. I believe changing to >=0.31.1 will work. |
Beta Was this translation helpful? Give feedback.
-
|
Latest react-native-nitro-modules 0.35.0 has a breaking change that affects react-native-iap. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It seem react-native-iap is pinned to react-native-nitro-modules@0.29.6. Marc has said nitro modules is fully backwards compatible so I do not think you need to pin it to a specific version. Maybe just set a min version?
Beta Was this translation helpful? Give feedback.
All reactions