René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"useOracleClock: return advance(ms), and fake performance (or document what it fakes)","articleBody":"Reported from an adopter's first session, at c58b0c2. Not yet reproduced here.\n\n**(a) Add an `advance(ms)` helper.** `useOracleClock` should return `advance(ms)`. Then drivers never import their own `vi`, which also avoids the problem in the two-Vitest-copies issue.\n\n**(b) Fake `performance`.** Today `toFake` covers setTimeout, clearTimeout, setInterval, clearInterval and Date (`src/oracle-property.ts` around line 1070). In the adopter's client, a deadline timer re-checks `performance.now()`, so a virtual timeout kept re-arming until real time caught up. Their workaround: `vi.spyOn(performance, 'now').mockImplementation(() => Date.now())`. Add `performance` to `toFake`, or at least list in the JSDoc exactly what it fakes.\n\nThis is a framework change, so it needs an oracle-first change (P9) to the framework self-oracle's controlled-clock law.\n\nThis issue was written by Isaac.\n","author":{"url":"https://github.com/KyleAMathews","@type":"Person","name":"KyleAMathews"},"datePublished":"2026-11-13T21:25:19Z","url":"https://github.com/TanStack/oracles/issues/67"}