-
Notifications
You must be signed in to change notification settings - Fork 2.2k
AngularFire breaking change between 5.1.3 and 5.2.0 #2115
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
Comments
Same issue as me: #2124 |
Glad I'm not alone haha |
Just turn off aot and you're good to go till its resolved. angular.json
|
ok cool. Yeah thanks, but that would affect our production environment too much then. So not an option for us. |
@jamesdaniels this issue got attention in the @LanderBeeuwsaert please rename this ticket to "Production Build Fail" or "Blank Screen of Death" so others can reach this easier, and figure that the only solution is to not optimize the bundle and get a ton of additional Mb in our bundle. |
@jamesdaniels Version 5.2 should be rolled back unless a fix is coming very soon. This AOT bug is catastrophic and makes this version useless. |
Refs #2117 |
Hello,
This is an issue regarding a breaking change going from AngularFire 5.1.3 to 5.2.0 that I'm unsure that it is the intention.
See the closed issue here: firebase/firebase-js-sdk#1837 ; closed because of a request to re-open here.
Could of course be that this is intended behaviour but I wouldn't think so.
The text was updated successfully, but these errors were encountered: