vitest-dev / vitest-dev/vitest

Use fakeTimers does not mock imports from `node:timers` or `node:timers/promises`

Open
#10,871 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

p3-minor-bug
Dominant language
TypeScript
Stars
17.1k
Forks
2k
Avg merge
1d 22h
Merged PRs (30d)
94

Description

Describe the bug

According to https://github.com/vitest-dev/vitest/pull/7097 this should work not, but it does not.

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-1gkfprhf?file=test%2Fbasic.test.ts

System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 22.22.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @vitest/ui: latest => 4.1.10 
    vite: latest => 8.2.0 
    vitest: latest => 4.1.10
Used Package Manager

npm

Validations

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked StackBlitz reproduction, especially test/basic.test.ts, and compare its behavior with the fake-timer expectations described in PR #7097. Trace the existing fakeTimers handling for node:timers and node:timers/promises, then add a regression test covering both imports; done when those imports are mocked consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.