-
Notifications
You must be signed in to change notification settings - Fork 12k
Tests fail with Angularfire #14280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think we have some errors being swallowed somewhere. |
Interesting, as far as I can tell something breaks mysteriously as soon as
It doesn't affect |
So this is a fun one. The above is enough to see it on a 8 RC project. But not on a new 7.0 project. Not even when the 7.0 project is updated to 8. In fact, it's not reproducible even after replacing every file in the 7 project with the 8 repro. At that point removing the package-lock.json and node modules, then reinstalling will indeed reproduce it. So it seems that it's something on an indirect loose, or hoisted, dependency. |
Ah good to know, this explains why the error occured only last week and not directly after updating to CLI 8. Any idea how we can find the root cause for this strange behaviour? |
I don't have a super good way to figure this out to be honest. Mostly trying to change dependencies and isolate where the problem came up. |
It seems to happen with |
#14334 should fix it. It seems like firebase might be doing something with polyfills starting on that version, and we were erroneously splitting polyfill chunks as well. |
Thank you very much for the quick fix @filipesilva |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Maybe
Description
When i run ng test i get
Executed 0 of 0 ERROR
🔬 Minimal Reproduction
Replace content of
app.component.ts
withand run
ng test
🔥 Exception or Error
🌍 Your Environment
Anything else relevant?
The text was updated successfully, but these errors were encountered: