Ivan Demchuk

@eemeli This, probably, can be closed now. #504 implements this functionality. Edit: And #218

@cbxp User time will be higher because Vitest is multi-threaded. User time is the time processor spent running a process. If you have multiple cores, user time will be higher...

@pmdarrow I'm investigating switching to `vm.runInNewContext` from `vm.runInThisContext`. This, hopefully, will allow us to drop costly isolation using Workers. We will essentially have the same isolation as Jest. But I...

After investigating it more and checking with @sheremet-va i don't think it can be implemented with current state of `vm` module. Fixing all the issues will mean getting all Jest...

@antfu `coverage-c8` and `coverage-istanbul` build is failing locally. ``` src/provider.ts(6,10): error TS2305: Module '"vitest/config"' has no exported member 'configDefaults'. ```

https://github.com/vitest-dev/vitest/runs/7835819196?check_suite_focus=true#step:6:107 Need to add `node` to tsconfig types

I like the idea. Another cool API could be `verify` or something like that. It will check that all setups were called. Idea stolen from C# Moq library - I'm...

+1 for making it a separate library. It would be useful with other test runners too. By the way, there it a `MoqJS` library: https://github.com/slavik57/moqjs. I did not think it...

https://github.com/bcoe/c8#checking-for-full-source-coverage-using---all `c8` by default only collects coverage for files that have been tested. You can pass `all: true` option to Vitest `coverage` config to report coverage for all files. You...

Your repository page returns 404. Is it private?