-
Notifications
You must be signed in to change notification settings - Fork 114
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
import package from firebase returns undefined #37
Comments
Unrelated to the router, but my first guess would be that firebase is using |
Indeed, not related to the router directly, but since the metro is a critical component of expo router. I posted here 😄 will do more digging later |
Updated the example to the latest version and cross-posted this issue in metro repo :) |
Confirming @EvanBacon's suspicions, @firebase/auth specifies top-level Workarounds for app devs
Follow-ups
|
Thanks so much for your time: @huntie created a PR on firebase side: firebase/firebase-js-sdk#6683 |
Thanks for the fix! @EvanBacon https://github.com/expo/expo/pull/19529/files according to the code, it should be fallback to the however, I tried it, still I am using this script, {
"scripts": {
"web": "EXPO_METRO_NO_MAIN_FIELD_OVERRIDE=false npx expo start --dev-client --web"
},
} What am I missing here? :) |
@Albert-Gao I'm struggling with this one too, as there's sparse examples for how to use metro resolver.resolveRequest. Our use-case is to have signInWithPopup and signInWithRedirect from firebase/auth. As of metro@0.74 it stopped working. resolverMainFields works without EXPO_METRO_NO_MAIN_FIELD_OVERRIDE for me on web. We have a native app too though so the first option is not viable. Could you share what you used for resolveRequest? |
Can not import package from firebase
w
to open the browserTest Firebase Auth
on the frontpagebrowserLocalPersistence
isundefined
Not happen on normal Expo web
repo here: (lib version: 0.22)
https://github.com/Albert-Gao/expo-router-web-try-out/tree/firebase-error
The text was updated successfully, but these errors were encountered: