-
Notifications
You must be signed in to change notification settings - Fork 634
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
Builds failing with 0.76.4 #979
Comments
Hi @erquhart - thanks for the report and investigation. As a first thought, if you're overriding Metro versions, could we rule out mismatched |
Ah I wasn't aware of those, looks I may need to override a few more packages. The overrides are based on requirements from I'll try overriding |
That fixed it - I'll give a heads up on the expo-router repo, thanks for the tip! |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
Using Expo managed workflow and Expo router, latest versions. But this seems metro specific.
Production builds fail with the following unhandled error:
The code producing this error was released in 0.76.4, and was added in this commit:
82bd64a
Reverting to 0.76.3 resolves the issue.
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
.Getting this reproduced in isolation would be a pretty complex task as I'm using Metro via EAS build. If nothing else I'm hoping this issue can corroborate with anyone else experiencing the same, as I'm not finding any mention of it anywhere.
What is the expected behavior?
Build succeeds.
Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.
Metro versions pinned via npm overrides and confirmed via
npm ls
.The text was updated successfully, but these errors were encountered: