-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Symbol-observable version upgrade causes typing mismatch with rxjs "unique symbol" #20248
Comments
Hi @saltdotac, I am not sure how to replicate the reported bug above. It is also strange to why It does appear that the RxJs team are considering rolling back this change as per ReactiveX/rxjs#5919 (comment) |
@alan-agius4 Here's what I get back from ls:
Also to clarify our new step is |
This is strange because in our CI and locally we run hundreds of @saltdotac, maybe you can share the project that encounter the problem? As, it is also strange that you are not getting the error constantly as type error like this should either happen always or never. |
I'm sorry, but we can't reproduce the problem following the instructions you provided. If the problem persists, please open a new issue following our submission guidelines. A good way to make a minimal repro is to create a new app via |
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?
Yes, the previous version in which this bug was not present was: 11.0.7Description
Symbol-observable changed their observable typing to unique symbol in 3.0.0, and rxjs does the same in their 7.0.0.beta9 but angular-cli uses 6.6.6. ReactiveX/rxjs#5919
I can't see how, but this problem seems nondeterministic. We don't see it every time we do run new then build, but occasionally.
🔬 Minimal Reproduction
ng new AngularDemo -g --directory . --force --routing --package-manager=yarn
ng build
🔥 Exception or Error
ng build fails with:
🌍 Your Environment
Anything else relevant?
The text was updated successfully, but these errors were encountered: