Open crisguitar opened 2 years ago
Did you try to reproduce by only using zone.js ? Seems likely that the problem comes from zonejs instead of our implementation
@vmarchaud I haven't. I'll give it a try and report back.
@vmarchaud I just confirmed that the issue comes from zone.js
. Setting __Zone_disable_ZoneAwarePromise
to true
makes the issue go away. How does that setting affect opentelemetry? I am not familiar with either library so I am not sure about the consequences.
For now I'm going to label this as P2 but it may end up being a bug in zone.js and not here. @vmarchaud since you already started looking into this can you take this issue?
@vmarchaud since you already started looking into this can you take this issue?
I answered because someone on slack asked a similar question few days ago (https://cloud-native.slack.com/archives/C01NL1GRPQR/p1660673184710719). I honestly don't think this is solvable for us as the problem is with upstream dependencies. I believe the best we can do is document when zonejs break so user know what to expect
I am also having problems with zone.js and a library which I am using. The library makes heavy use of async-generators and this seems to completely break the functioning of zone.js.
Is there any plausible alternative to using zone.js when using async/await in the browser?
What happened?
Steps to Reproduce
ZoneContextManager
in any sveltekit appafterNavigate
lifecycle functionExpected Result
Code inside
afterNavigate
is called normallyActual Result
Code inside
afterNavigate
is not called; however, if you navigate away from the page the callback is called. This suggests the callback was registered too late. Somehow importingZoneContextManager
breaks how sveltekit is rendering and registering callbacks.Additional Details
I created a repo to reproduce this: https://github.com/crisguitar/after-navigate-issue
OpenTelemetry Setup Code
package.json
Relevant log output
No response