Hi there!

We´re using AppLauncKit v2 to scaffold our project. We´ve tried to update the expo app (frontend/apps/expo) to the latest SDK version (52.0.7) following the [official guide](https://expo.dev/changelog/2024/11-12-sdk-52#%EF%B8%8F-upgrading-your-app).

First I was getting dependency resolution error

cooty@cooty:~/Work/msb-2.0/frontend (chore/updtate-expo-sdk-to-52)$ npm install --ws
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: app-launch-kit-expo-app@1.0.0
npm error Found: expo@52.0.7
npm error node_modules/expo
npm error   expo@"^52.0.7" from app-launch-kit-expo-app@1.0.0
npm error   apps/expo
npm error     app-launch-kit-expo-app@1.0.0
npm error     node_modules/app-launch-kit-expo-app
npm error       workspace apps/expo from the root project
npm error   peer expo@"*" from @expo/dom-webview@0.0.1
npm error   node_modules/@expo/dom-webview
npm error     peerOptional @expo/dom-webview@"*" from expo@52.0.7
npm error
npm error Could not resolve dependency:
npm error peer expo@"^49.0.7 || ^50.0.0-0" from @expo/webpack-config@19.0.1
npm error node_modules/@expo/webpack-config
npm error   @expo/webpack-config@"~19.0.1" from app-launch-kit-expo-app@1.0.0
npm error   apps/expo
npm error     app-launch-kit-expo-app@1.0.0
npm error     node_modules/app-launch-kit-expo-app
npm error       workspace apps/expo 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.

So it failed because of expo/webpack-config, which is understandable cause even Expo 51 doesn´t support bundling with Webpack anymore.