if performance.timeOrigin is 0, use performance.now() directly in Clock

[tim-smart]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: c132863

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 30 packages

Name	Type
effect	Patch
@effect/cli	Patch
@effect/cluster-browser	Patch
@effect/cluster-node	Patch
@effect/cluster-workflow	Patch
@effect/cluster	Patch
@effect/experimental	Patch
@effect/opentelemetry	Patch
@effect/platform-browser	Patch
@effect/platform-bun	Patch
@effect/platform-node-shared	Patch
@effect/platform-node	Patch
@effect/platform	Patch
@effect/printer-ansi	Patch
@effect/printer	Patch
@effect/rpc-http	Patch
@effect/rpc	Patch
@effect/schema	Patch
@effect/sql-d1	Patch
@effect/sql-drizzle	Patch
@effect/sql-mssql	Patch
@effect/sql-mysql2	Patch
@effect/sql-pg	Patch
@effect/sql-sqlite-bun	Patch
@effect/sql-sqlite-node	Patch
@effect/sql-sqlite-react-native	Patch
@effect/sql-sqlite-wasm	Patch
@effect/sql	Patch
@effect/typeclass	Patch
@effect/vitest	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[johtso]

After some investigation it seems like this is an inconsistency between miniflare and the live cloudflare runtime. Really Date.now() and performance.now() should both return 0.. but due to a quirk in miniflare Date.now() returns the current time even pre-io, but performance.now() returns 0.

cloudflare/workers-sdk#6261