-
Notifications
You must be signed in to change notification settings - Fork 191
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
Expo example yields "Unable to resolve module ./.expo/.virtual-metro-entry" #722
Closed
1 of 2 tasks
Labels
bug
Something isn't working
Comments
Currently expo example is only supported for JS-only modules. So this is not a valid combination. |
satya164
added a commit
that referenced
this issue
Dec 8, 2024
currently the arguments are not validated correctly since they are validated against filtered questions. this fixes it to validate against the full list of questions. this should avoid cases like #722
satya164
added a commit
that referenced
this issue
Dec 8, 2024
currently the arguments are not validated correctly (#722) since they are validated against filtered questions. this fixes it to validate against the full list of questions. this also refactors the prompts module to move argument handling to the prompt function.
satya164
added a commit
that referenced
this issue
Dec 8, 2024
currently the arguments are not validated correctly (#722) since they are validated against filtered questions. this fixes it to validate against the full list of questions. this also refactors the prompts module to move argument handling to the prompt function.
satya164
added a commit
that referenced
this issue
Dec 8, 2024
currently the arguments are not validated correctly (#722) since they are validated against filtered questions. this fixes it to validate against the full list of questions. this also refactors the prompts module to move argument handling to the prompt function.
satya164
added a commit
that referenced
this issue
Dec 8, 2024
currently the arguments are not validated correctly (#722) since they are validated against filtered questions. this fixes it to validate against the full list of questions. this also refactors the prompts module to move argument handling to the prompt function.
satya164
added a commit
that referenced
this issue
Dec 8, 2024
currently the arguments are not validated correctly (#722) since they are validated against filtered questions. this fixes it to validate against the full list of questions. this also refactors the prompts module to move argument handling to the prompt function.
satya164
added a commit
that referenced
this issue
Dec 8, 2024
currently the arguments are not validated correctly (#722) since they are validated against filtered questions. this fixes it to validate against the full list of questions. this also refactors the prompts module to move argument handling to the prompt function.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Instantiating a library with an expo example leads to the following error when starting app and loading the bundle via the Metro dev-server:
Searching ☝ lead me to react-native-community/upgrade-support#248 (comment)
I believe the root cause is this file templates/example-common/example/metro.config.js overrides this file templates/expo-library/example/metro.config.js.
Packages
Selected options
I ran
Link to repro
N/A
Environment
The text was updated successfully, but these errors were encountered: