oh wow

Work around? None, really - but it depends what accuracy you want

It's intentionally inaccurate, and any workarounds to update the time are varyingly inaccurate.

i need accuracy += 100ms

it's a timer for a game server

When you're doing I/O (fetch, KV, cache, etc) then it'll update somewhat

If you're just doing compute in the Worker, don't expect any updates

i need updates though lol

You can use a remote timing source that's probably sub-50ms of latency, but that's about it

You can use

await scheduler.wait(ms)

or what Walshy posted, just keep in mind that the timer that backs those timeouts is Spectre-safe so it won't really wait that many milliseconds, but it should be close.

I always forget scheduler.wait, much better

i.e

Date.now()

,

fetch(..., { signal: AbortSignal.timeout(1000) })

,

Date.now()

will give you a delta of 1000 - but it isn't really 1000ms of wall-clock time, but it should be close enough for your use-cases imo

my favourite API

yeah this is a turn-based game, so i really do not care about accuracy very much at all

if a human wouldn't notice it's off, it doesn't matter

probably 100ms is plenty

Sleeps will advance the clock, with varying inaccuracy (lots of CPU = lots of inaccuracy) - see if

await scheduler.wait(1); Date.now()

is good enough for you

i still don't understand why Date.now() is frozen in

--local

but not in

--experimental-local

?

Not being done in

--local

is likely just a discrepancy between development and production since

--local

is a Node emulation whereas

--experimental-local

uses the open-source runtime

i'll need

node_compat = true

right?

Miniflare freezes unless you do --real-time (though the way it freezes the time isn't 1:1 with Workers)

That's just for some Node polyfills - it depends on your code (and dependencies)

They're not the best, and

compatibility_flags = ["nodejs_compat"]

is better ones built into the runtime - but there aren't very many modules covered by it just yet

It shouldn't need to be imported

i'm just trying to call

scheduler.wait()

No need for an import

It exists on the global scope as-is

Pretty much all of the Workers APIs sit on

globalThis

- the only things that need importing is the Node polyfills if you use those