refactor(expotv): enable Expo autolinking module resolution#10
Merged
anishamalde merged 1 commit intoAmazonAppDev:mainfrom Apr 7, 2026
Conversation
This aligns Metros own module resolution with the core libraries resolved from autolinking. It makes working in a monorepo easier and more stable when using multiple versions of React Native. This is an opt-in for SDK 54, and is enabled by default in SDK 55. See: https://docs.expo.dev/versions/latest/config/app/\#autolinkingmoduleresolution See: https://docs.expo.dev/modules/autolinking/\#dependency-resolution-and-conflicts See: https://docs.expo.dev/guides/monorepos/\#deduplicating-auto-linked-native-modules
anishamalde
approved these changes
Apr 7, 2026
Contributor
anishamalde
left a comment
anishamalde
left a comment
There was a problem hiding this comment.
Thank-you again for the PR & Context! Merged ✅
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changes:
experiments.autolinkingModuleResolution: trueinpackages/expotvAs a follow-up of #8, I also spotted that Vega is running React Native 0.72 - while ExpoTV is running React Native 0.81. In these cases, where multiple React Native versions live inside a single monorepo, I think it's a good idea to turn on our special resolver to align what was autolinked with what should be resolved. It makes working in a monorepo easier and more stable when using multiple versions of React Native.
See: https://docs.expo.dev/versions/latest/config/app/\#autolinkingmoduleresolution
See: https://docs.expo.dev/modules/autolinking/\#dependency-resolution-and-conflicts
See: https://docs.expo.dev/guides/monorepos/\#deduplicating-auto-linked-native-modules
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.