You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like npm i @logto/rn or npx expo install @logto/rn won't work directly with expo sdk 52 unless the --legacy-peer-deps flag is added due to version conflict. Is there any plan to perform version bump for https://www.npmjs.com/package/@logto/rn so that it works directly with expo sdk 52?
Relevant logs:
npm i @logto/rn
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/expo-web-browser
npm error expo-web-browser@"~14.0.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer expo-web-browser@"^13.0.3" from @logto/[email protected]
npm error node_modules/@logto/rn
npm error @logto/rn@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Seems like
npm i @logto/rn
ornpx expo install @logto/rn
won't work directly with expo sdk 52 unless the--legacy-peer-deps
flag is added due to version conflict. Is there any plan to perform version bump for https://www.npmjs.com/package/@logto/rn so that it works directly with expo sdk 52?Relevant logs:
Beta Was this translation helpful? Give feedback.
All reactions