James Daniels

Our test suite uses i18n FYI, see our [angular.json](https://github.com/firebase/firebase-tools/blob/a6f052ea4dc1e1248023ddc27361f7e4f479e390/scripts/webframeworks-deploy-tests/angular/angular.json#L39) and [server.ts](https://github.com/firebase/firebase-tools/blob/a6f052ea4dc1e1248023ddc27361f7e4f479e390/scripts/webframeworks-deploy-tests/angular/server.ts#L13)

@JGSolutions "support" is a loaded term, we are not a supported product as it related to the Google Cloud terms of service—but there are people working on the library. AngularFire...

@JGSolutions no worries. Yeah, that's the error that caused us a lot of grief in our test suite. It turns out that the rxjs-interopt pipe we're using in our methods...

@JGSolutions our zone wrappers will now noop when outside of an injector context, cutting `rc.3` now, give that a spin and LMK how it goes

yeah I caught that one earlier today, addressing in #3590

Rc.4 out.

I don't foresee any large changes in the next two weeks, if you're seeing good behavior in local prod mode go for it. Just be ready to roll back incase...

Yes, those warnings are safe to ignore and are just breadcrumbs incase you run into any zone / rehydration instabilities. We have docs for that inbound.

Since this is an `@angular/core` I'd recommend filing a bug over in https://github.com/angular/angular. Is it crashing during the SSR or CSR cycle? Node and browser versions will be helpful to...

As seen in your error message, the cause of this is in Firebase JS SDK namely `@firebase/auth`. This should be addressed in Firebase JS SDK v11, which we are working...