This seems to be in angular/core
If we revert to firebase-js-sdk 10 and angularFire 18 the issue disappears.
It doesn't happen on our dev builds (esbuild) but it does happen when we deploy to production.
So my non-expert guess would be that treeshaking is somehow involved?