adamstret
adamstret
@anandsathe67 can you please share with us how to apply the patch? Do I just drop that txt file somewhere in the node_modules in the project? Or do I have...
@anandsathe67 way too complicated for me :( guess I will have to wait until this plugin gets fixed, or until some good soul forks & fixes it... :(
What exactly is the reason behind the 5sec delay? Can't we just run 1.buildWatch 2.killPorts 3.getConfig 4.emulatorsStart one after another?
@simondotm I still don't get it. You're saying that "we could have a scenario where the emulator starts before the initial build is completed...". We can wait for one process...
I'm not forgeting it, I didn't know it :) thanks for clarifying it for me.
This is what you end up with when you have slobs work on a project. The Firebase team is long overdue for some serious "reshuffling". And by "reshuffling" I mean...
A lot of people suggest [this workaround](https://github.com/angular/angularfire/pull/3590#issuecomment-2581455741) BUT is there a REAL solution? OR is this a ZONE.js problem that will go away only once ZONE.js is gone from Angular?
@rgant so those warnings are something like "false positives" and can be fully ignored? If so, did the Angular team miss an edge case when implementing this functionality? I need...
I've never said that people on the angular _team_ were incompetent :) IMHO they're the dopest bunch. A bit off topic, but what do you mean by "The team is...
Oh I see, Anyways, as you suggested, I'll just ignore those warnings and keep up hope that Angular dumps zone.js in the near future. Thanks.