Results 43 comments of Connor Dooley

@Sardor01 You don't have to mount the stub, but other than that yes that looks right to me

I'm having this issue too, despite what it says in the readme

currently I'm using the pancurses backend. I'll try to reproduce, I've been working on the program some more and haven't gotten the error again but I'll see if I can...

Oh yeah probably should have posted my specs - OS: Windows 10 Home - rustc version 1.22.1 - Using the most recent git version of Cursive

I am having the same issue that @SuspiciousLookingOwl is having, and it only seems to happen with `"strict": true` in the tsconfig. Without strict being on the narrowing performs as...

I've made a reproduction of the bug with v-for here: https://github.com/dospunk/vetur-v-if-not-infering-bug The error reported by Vetur on line 4 of test.vue should not be there

I'm having the same problem as @OmgImAlexis

@trurl-master Vitest is "compatible" with jest in that it defines most of its APIs to be compatible, but it doesn't support things like accessing the `jest` global variable directly so...

It works! Having to set toFake on vi.useFakeTimers every time is a bit clunky but just a limitation of the library I suppose. The only issue I had is having...

I'm having the same issue with `:focus-within` and jsdom as well. The error stack trace does come back to nwsapi The relevant lines of the stack trace are: ``` at...