-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right-hand side of 'instanceof' is not an object / FailedToResolveUnsupportedError #1393
Comments
Hi @aldebout - the problematic line there is That's an explicit dependency of Could you verify that the version of |
(CC @byCedric on the remote possibility that Expo CLI is doing anything funny with |
@robhogan I'm also very confused as to how something this basic can fail, I'll try looking at the local files themselves. Edit: I checked locally in my node_modules and everything looks fine. The types for metro-resolver don't really match the js but that should not be a problem. What I really don't understand is that a few lines above the problematic one is a very similar check:
I fail to see a structural difference between This is the output of
|
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When adding
unstable_enablePackageExports = true
to config and starting the dev server withexpo dev
, the app crashes and it looks like there's an issue with error reporting inside of metro.If the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can
yarn install
andyarn test
.Not sure how to repro since I think there's an underlying issue with my repo but this is about the failure to properly throw the error.
What is the expected behavior?
I get a useful error.
Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.
node: 20.16.0
pnpm: 9.6.0
os: macos Sonoma 14.7
metro: 0.81.0
expo: 52.0.7
RN: 0.76.2
Project is in a pnpm + turborepo monorepo.
Full metro config:
The text was updated successfully, but these errors were encountered: