fix(metro-config): add missing @expo/spawn-async@^1.7.2
dependency
#26021
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
@expo/metro-config
does not have a direct dependency reference to@expo/spawn-async
, yet we import it insrc/serializer/exportHermes.ts
. This breaks isolated modules.There is no (implicit) dependency chain, the only unrelated chain exists from a direct project dependency:
expo → @expo/cli → @expo/spawn-async
How
@expo/spawn-async@^1.7.2
as dependency to@expo/metro-config
Test Plan
See if
yarn typecheck
has any typescript issues.Checklist
npx expo prebuild
& EAS Build (eg: updated a module plugin).