Skip to content
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

fix(metro-config): fix async bundling #25901

Merged
merged 2 commits into from
Dec 13, 2023

Conversation

EvanBacon
Copy link
Contributor

@EvanBacon EvanBacon commented Dec 13, 2023

Why

How

Test Plan

  • Nothing in place to prevent this from regressing. We should probably have e2e web tests now.

Checklist

Copy link
Member

@ide ide left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question for Cedric: in #25804, was the most important change to make @expo/metro-config be a dependency of expo, which this PR does not change? Or do we want to revert the change to expo's package.json?

Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
@expo-bot expo-bot added bot: passed checks ExpoBot has nothing to complain about and removed bot: suggestions ExpoBot has some suggestions labels Dec 13, 2023
@EvanBacon
Copy link
Contributor Author

@ide I think this was just a basic misunderstanding of how two undocumented redundant layers in Metro work, otherwise the original change is still valid for module isolation. We'll get e2e tests in place and ensure this doesn't happen again.

@EvanBacon EvanBacon merged commit 45ba654 into main Dec 13, 2023
11 checks passed
@EvanBacon EvanBacon deleted the @evanbacon/metro-config/fix-async-routes branch December 13, 2023 04:16
@brentvatne brentvatne added the published Changes from the PR have been published to npm label Dec 13, 2023
onizam95 pushed a commit to onizam95/expo-av-drm that referenced this pull request Jan 15, 2024
# Why

- fix regression in expo#25804

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan

- Nothing in place to prevent this from regressing. We should probably
have e2e web tests now.

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: fingerprint changed bot: passed checks ExpoBot has nothing to complain about published Changes from the PR have been published to npm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants