Tasks (tests, suites, hooks) that are too fast show a duration of 0ms in Task results

[JessicaSachs]

Clear and concise description of the problem

I was writing a custom reporter and noticed that many of the tasks I was working with were showing 0ms as their duration. Upon further digging, I noticed that Vitest uses Date.now for a lot of measurements related to timing.

I asked @sheremet-va why that is, and he mentioned that global.performance required an import from node:performance at the time of writing. Importing from node:performance would've broken browser mode for Vitest, so the team elected to use the more compatible (but less precise) Date.now to take measurements.

Suggested solution

Now that global.performance is available in all node versions that Vitest supports, we can go through everything to do with timings and swap from using Date.now to using global.performance

Alternative

We could decide not to do this.

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[LuciNyan]

I'd be happy to take on this issue. Could you assign it to me? 👀