analytics-react-native icon indicating copy to clipboard operation
analytics-react-native copied to clipboard

Throwing dependency issues when building for RN 0.74+

Open pTinosq opened this issue 1 year ago • 0 comments

We are looking to upgrade to RN 0.74.4 and have found that this package is throwing issues where the peer dependency with @react-native-async-storage/async-storage is not compatible. This error started appearing when we upgraded @react-native-async-storage/async-storage to v2.0.0. Would it be possible to update the library so it is compatible with 2.0.0?

  • analytics-react-native version: ^2.19.4
  • Integrations versions (if used): "@react-native-async-storage/async-storage": "^2.0.0"
  • React Native version: 0.74.3
  • iOS or Android or both? Android

Steps to reproduce

  1. Upgrade "@react-native-async-storage/async-storage": "^2.0.0"
  2. Try and run npm i

Expected behavior It should install all packages with no issue

Actual behavior

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @segment/[email protected]
npm ERR! Found: @react-native-async-storage/[email protected]
npm ERR! node_modules/@react-native-async-storage/async-storage
npm ERR!   @react-native-async-storage/async-storage@"^2.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @react-native-async-storage/async-storage@"1.x" from @segment/[email protected]
npm ERR! node_modules/@segment/analytics-react-native
npm ERR!   @segment/analytics-react-native@"^2.19.4" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @react-native-async-storage/[email protected]
npm ERR! node_modules/@react-native-async-storage/async-storage
npm ERR!   peerOptional @react-native-async-storage/async-storage@"1.x" from @segment/[email protected]
npm ERR!   node_modules/@segment/analytics-react-native
npm ERR!     @segment/analytics-react-native@"^2.19.4" 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.

pTinosq avatar Sep 03 '24 15:09 pTinosq