Issue with `Clock.currentTimeNanos` in Cloudflare Workers with `nodejs_compat` flag affecting `@e...
Is anyone using cloudflare workers with effect? I stumbled upon an issue where
I'd very much appreciate if someone could confirm this problem. I created a simple example here https://github.com/bastiankistner/effect-clock-test . It's just a wrangler init starter where you need to run
1.
2.
for 1. it should state something like
and for 2. it should be much lower like
I would assume I can provide an alternative implementation of the Clock service, similar to the default logger? I'll see if that could solve my little problem. But it'd be also great if someone could confirm that this indeed might be an issue. Thanks a lot!
Clock.currentTimeNanoscompatibility_flags@effect/opentelemetrystartTimenodejs_compatClock.currentTimeNanosnodejs_compatcurrentTimeNanosI'd very much appreciate if someone could confirm this problem. I created a simple example here https://github.com/bastiankistner/effect-clock-test . It's just a wrangler init starter where you need to run
pnpm install1.
pnpm run devhttp://localhost:8787/2.
pnpm run dev-compathttp://localhost:8787/for 1. it should state something like
Clock.currentTimeNanos: 1745444706401999872and for 2. it should be much lower like
Clock.currentTimeNanos: 624000000I would assume I can provide an alternative implementation of the Clock service, similar to the default logger? I'll see if that could solve my little problem. But it'd be also great if someone could confirm that this indeed might be an issue. Thanks a lot!
Similar Threads
Was this page helpful?
