-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Module has no exported member error after upgrading to v7.0.0 #2901
Comments
Good catch, I'd recommend using |
@jamesdaniels Does angularFire reference |
@Feiyang1 no direct use, I think Angular's typescript configuration chases the dependencies by default. |
same as #2853 |
Please feel free to close this issue a duplicate, at your discretion. 🙂 Thanks for filing an issue over here firebase/firebase-js-sdk#5382, @CoooWeee! 🙇 |
Ty |
@jamesdaniels Solution I created a video and GitHub Repo with the fix I live for now, appreciate your teams hard work on the major release. Great show many, optimisations + features, i'm lovin it! |
Quick report for visibility.
Easy enough to work around, maybe it's an issue with my setup? I'm currently working on a big client project due today, but should have time to circle back and take a closer look this evening.
Grats on the release! 🍻
Version info
Angular: 12.2.2
Firebase: 9.0.0
AngularFire: 7.0.0
Browser: Chrome v92.0.4515.159
Operating System: macOS Big Sur v11.5.2
Other (e.g. Ionic/Cordova, Node):
How to reproduce these conditions
Upgrade to AngularFire 7.0.0 via the upgrade guide.
Debug output
Expected behavior
Consistently clean builds after upgrading to AngularFire v7.0.0. 👌
Actual behavior
Workaround
I was able to quickly get around this issue by substituting the missing import for one I found in an adjacent types library:
node_modules/@firebase/app-compat/dist/src/firebaseApp.d.ts
Remove:
Add:
Diff:
I'd be surprised if this is an ideal solution, but it got me back up and running for now. I should have time to revisit this again later this evening / tomorrow. 🙃
The text was updated successfully, but these errors were encountered: