Rank, 14 days: 3 on the Bun sheet
2 people reported

All time, since Nov 1.

clearAllTimers() throws

“When importing vi from vitest, vi.clearAllTimers() throws if fake timers are inactive.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/bun/issues/23870/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

clearAllTimers() throws when fake timers are not active. In bun test, jest.clearAllTimers() and vi.clearAllTimers() throw with real timers, breaking shared afterEach cleanup; Jest and Vitest treat it as a no-op.

Is this your bug?

File my report
Where
bun test
Error text
Fake timers are not active. Call useFakeTimers() first.
Versions
1.4.4-canary.1
Platforms
Linux, macOS
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. bun test: jest.clearAllTimers() throws when fake timers are not active (Jest and Vitest treat it as a no-op)#48138
  2. bun test: vi.clearAllTimers() throws with real timers, unlike Vitest#47657

Do you work on Bun?

Claim its RAP Sheet to see what your users report and answer them in one place.