Releases: angular/angularfire
5.4.0
5.3.1
Bug Fixes
- schematics: The schematics should be functional again. The version of
firebase-tools
we were installing when you calledng add @angular/fire
was using deprecated API. (#2285) (5867eeb) - schematics: fix issues with FS and Devkit Paths (#2279) (5ccf5db)
- rc: Need to
ensureInitialized()
(#2290) (0d95523)
6.0.0-rc.0
Version 6 of AngularFire drops support for Angular version 8 and below, older versions of typescript, Firebase, drops firebase-node
, database-deprecated
, and more.
- Support for Angular versions less than 9 has been dropped
- Support for Firebase versions less than 7.8 has been dropped
- Support for
firebase-tools
less than 7.12 has been dropped angularfire2
NPM shim will no longer be updated- Dropped
@angular/fire/firebase-node
and@angular/fire/database-depreciated
- Using
ng-packagr
to build the library, bringing us back up to speed on APF - All of our
@NgModules
are nowprovidedIn: 'any'
rather than singletons - We make use of Proxy in more modules, you'll need to polyfill if you want to support IE 11
@angular/fire
- Dropped the
RealtimeDatabaseURL
andDATABASE_URL
DI tokens, useimport { URL } from '@angular/fire/database'
instead - Dropped
runOutsideAngular
,runInZone
,FirebaseZoneScheduler
, and theFirebase*
type aliases
@angular/fire/analytics
AngularFireAnalytics
now memoziesanalytics.Analtyics
instances keyed to themeasurementId
, this prevents exceptions if you're using more than oneFirebaseApp
with the samemeasurementId
. This is also needed as we areprovidedIn: 'any'
.
@angular/fire/auth
AngularFireAuthModule
is now side-effect free andAngularFireAuth
will dynamically importfirebase/auth
when a request is madeAngularFireAuth
has dropped theauth
property and instead Promise Proxies the underlying Firebaseauth.Auth
instance
@angular/fire/auth-guard
AngularFireAuthGuard
andcanActivate
have dropped (attempted) support for rawAuthPipe
s, as they were not functioning in AOT builds; you'll want to move toAuthPipeGenerator
s
@angular/fire/database
AngularFireDatabaseModule
no longer importsfirebase/database
on it's own to remain side-effect free, you'll need toimport 'firebase/database'
on your own- Dropped the
RealtimeDatabaseURL
andDATABASE_URL
DI tokens in favor ofURL
@angular/fire/firestore
AngularFirestoreModule
no longer importsfirebase/firestore
on it's own to remain side-effect free, you'll need toimport 'firebase/firestore'
on your own- Dropped the
EnablePersistenceToken
DI token in favor ofENABLE_PERSISTENCE
- Dropped the
PersistenceSettingsToken
DI token in favor ofPERSISTENCE_SETTINGS
- Dropped the
FirestoreSettingsToken
DI token in favor ofSETTINGS
@angular/fire/functions
- Dropped the
FunctionsRegionToken
andFUNCTIONS_REGION
DI tokens in favor ofREGION
- Dropped the
FUNCTIONS_ORIGIN
DI token in favor ofORIGIN
AngularFireFunctionsModule
is now side-effect free andAngularFireFunctions
will dynamically importfirebase/functions
when a request is madeAngularFireFunctions
has dropped thefunctions
property and instead Promise Proxies the underlying Firebasefunctions.Functions
instance
@angular/fire/messaging
AngularFireMessaging
's dynamic import offirebase/messaging
is now lazy, if you don't call any methods the SDK will not be loadedAngularFireMessaging
has dropped themessaging
property and instead Promise Proxies the underlying Firebasemessaging.Messaging
instance
@angular/fire/performance
AngularFirePerformance
has dropped theperformance
property and instead Promise Proxies the underlying Firebaseperformance.Performance
instance
@angular/fire/storage
AngularFireStorageModule
no longer importsfirebase/storage
on it's own to remain side-effect free, you'll need toimport 'firebase/storage'
on your own- Dropped
StorageBucket
DI token in favor ofBUCKET
5.3.0
AngularFire 5.3 introduces Analytics and Remote Config modules.
5.3.0-rc.4
Final candidate for 5.3.0.
AngularFireAnalytics
andAngularFireRemoteConfig
should be safe in non-browser environments (mostly noop due to lack of support in the Firebase libraries, but should not cause runtime exceptions)ScreenTrackingService
should now be more reliable in reporting your component's selector (asscreen_name
), especially in AOT mode.- To better facilitate debugging,
ScreenTrackingService
will console logscreen_view
events whenDEBUG_MODE
is enabled.
Please test that screen_class
attribute is correct tracking your component's selector in Google Analytics for the ScreenTrackingService
both against AOT and JIT. There's some hard to test code here. Report your experience on #2187
5.3.0-rc.3
Continued work on AngularFireRemoteConfig
and AngularFireAnalytics
, see #2187
5.3.0-rc.2
Continued work on AngularFireRemoteConfig
and AngularFireAnalytics
, see #2187
5.3.0-rc.1
Continued work on AngularFireRemoteConfig
and AngularFireAnalytics
, see #2187
5.3.0-rc.0
Added AngularFireAnalytics
, AngularFireRemoteConfig
, and refactored the DI Tokens across the project. See #2187 for more details.