Unable to resolve import of file after upgrading from SDK 48 to 51 in monorepo

[jesuscovam]

Minimal reproducible example

see summary for reference

What platform(s) does this occur on?

iOS

Did you reproduce this issue in a development build?

No (tested in Expo Go)

Summary

I'm trying to upgrade two expo apps inside a yarn monorepo, the apps were on the SDK 48 and after upgrading to 51 they won't start, they are trying to import a file from within expo from the root of the monorepo but I'm not sure why or which dependency should be update to include it

Environment

expo-env-info 1.2.0 environment info:
System:
OS: macOS 14.1.2
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.8.0 - /opt/homebrew/bin/node
Yarn: 1.22.10 - /opt/homebrew/bin/yarn
npm: 10.2.3 - /opt/homebrew/bin/npm
Watchman: 2023.12.04.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.1 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.5, iOS 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5
Android SDK:
API Levels: 33, 33, 34
Build Tools: 30.0.3, 33.0.2
IDEs:
Xcode: 15.4/15F31d - /usr/bin/xcodebuild
npmGlobalPackages:
eas-cli: 9.0.6
expo-cli: 6.3.10
Expo Workflow: managed

Expo Doctor Diagnostics

[gopidon]

Same here. I upgraded from 49 to 50. Expo is unable to resolve file paths. For example:

In my App.js , I refer to local files using absolute path like import xyzzy from 'gst/apollo/client', where 'gst' is the main directory in which all my expo code exists. All these imports are failing at bundle time.

[gopidon]

Solution for me:

1. npm i babel-plugin-module-resolver
2. modify babel.config.js

plugins: [
['module-resolver',
{
alias: {
gst: '.',
},
}
]
],

[jesuscovam]

Solution for me:

1. npm i babel-plugin-module-resolver
2. modify babel.config.js

plugins: [ ['module-resolver', { alias: { gst: '.', }, } ] ],

Thanks for the help! But this wasn't for me 😢

What I'm understanding is that 'expo-modules-core' shouldn't be something I install in my managed expo apps, its like main package for expo installing expo packages in react-native (not managed) apps, but its also a inner dependency of the new expo 51 SDK.