next-adapter needs deps bumped

[Distortedlogic]

Summary

the peer dep for next-adapter is expo ^46 but expo is now on ^49

Environment

any

Please specify your device/emulator/simulator platform, model and version

n/a

Error output

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: mobile@0.0.1
npm ERR! Found: expo@49.0.9
npm ERR! node_modules/expo
npm ERR!   expo@"49.0.9" from mobile@0.0.1
npm ERR!   apps/mobile
npm ERR!     mobile@0.0.1
npm ERR!     node_modules/mobile
npm ERR!       workspace apps\mobile from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer expo@"^46" from @expo/next-adapter@5.0.2
npm ERR! node_modules/@expo/next-adapter
npm ERR!   dev @expo/next-adapter@"5.0.2" from mobile@0.0.1
npm ERR!   apps/mobile
npm ERR!     mobile@0.0.1
npm ERR!     node_modules/mobile
npm ERR!       workspace apps\mobile 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.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\jerme\AppData\Local\npm-cache\_logs\2023-09-08T11_57_11_647Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: C:\Users\jerme\AppData\Local\npm-cache\_logs\2023-09-08T11_57_11_647Z-debug-0.log

Reproducible demo or steps to reproduce from a blank project

just install

[robdubparker]

+1

[mdottavi]

same here

[mdottavi]

Hi, I understand this is unofficial and not a first-class Expo feature, but some feedback is needed for the issue progress.

[pkreissel]

I used this in my package.json and all the errors went away.

"overrides": { "@expo/next-adapter": { "expo": "$expo", "react-native-web": "$react-native-web" } }

[byCedric]

See: https://github.com/expo/examples/pull/449