-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(core): Support Firebase v8 (#2624)
* feat: update AngularFire to be compatible with Firebase JS SDK v8 Co-authored-by: Sarun Intaralawan <sarunint@sarunint.com>
- Loading branch information
1 parent
98e5046
commit 082c0de
Showing
34 changed files
with
2,171 additions
and
2,859 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
082c0de
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has nothing to do with
angularfire
but do you know why firebase stopped letting you import destructured types, and why they now require everything to be dot-referenced fromfirebase
? Thank you in advance!082c0de
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sambecker great question. Ultimately with ES module you can't use default exports and namespaces at the same time, it's weird I know. Firebase v7 had a bunch of work arounds for this & they were getting really messy, ultimately they decided to break when they fixed their package.json so ngcc would stop freaking out about CJS builds. I'm not a fan of default exports in general but it was decided this would be the less drastic API change for now. There is however a modular version of the js sdk on the way, it's being developed in the open on that github repo, so check it out if you're curious. I'll be starting an experimental branch of rxfire & angularfire to support it soon.
082c0de
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @jamesdaniels for that thoughtful reply! Makes total sense that firebase would make this move as part of a larger migration. Will definitely follow your experimental branch. So glad you updated your library so quickly. Looking at this commit was extremely helpful. Could not find the equivalent direction from Google!