Description

WIP

While checking #7329, I was slightly confused about this feature allowing mocking date vi.setSystemTime without vi.useFakeTimers. I'd assume historically Vitest had "mockdate" feature (vi.mockCurrentDate), which is later replaced with Jest-like API vi.setSystemTime #531, but then that required vi.useFakeTimers, so vi.setSystemTime only mocking is added back in #639.

Having two system internally (and two flags _fakingTime and _fakingDate) looks confusing and maybe removing this is fine later time on breaking change. Users can probably migrate to vi.useFakeTimers({ toFake: ["Date"] }).

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.