Adding global caches to survive/warn on HMR, cleanup, etc.

[jamesdaniels]

• Adding global instance caches to the modules, so they don't freak out when HMR is enabled (HMR t v6.1.0 RC3: Firestore Emulators Error: Precondition failed #2655). This takes on globalThis as a needed polyfill for many environments.
• If injected settings for modules are changed after they are initialized you will receive a warning and the prior instance will be returned (ignoring the changes), this is especially important for HMR. If HMR is detected there will be an additional warning suggesting they do a full reload to see the changes.
• Added a polyfill table and notes about why we version like we do
• Adding more convoluted stuff to my sample app to flex AngularFire
• Internal cleanup on AngularFireAnalytics
• AngularFireAnalytics will now wait for UserTrackingService to detect the user before sending the screen_view event, if UserTrackingService has been provided
• Adding a warning if the Auth Emulator is detected in conjunction with AngularFirestore and AngularFireDatabase as they will invalidate the emulated auth token before the dynamic import of firebase/auth is completed (Firestore emulator calls Google APIs to check auth token #2656)
• Warn if we absorbed an error keeping Firestore persistence from enabling
• Logging sign_up and login events in UserTrackingService
• Adding credential observer to AngularFireAuth

[volago]

Hi.

I've notice that credentials are available just after user logging. When I refresh the page, user is still logged, but credentials are null. Is it desired behavior?

Where can I get accessToken (for download Facebook avatar) when user is already logged in?

[jamesdaniels]

@volago Yes, this is expected behavior with Firebase. If you need persistence for the access token you'll need to do that yourself, toss it in Firestore/Database perhaps? Make sure to lock it down with security rules.