Valera Trubachev

I am experiencing this too (very similar reproduction to the repo linked in the initial report), but with `@vue/[email protected]` and `[email protected]` - adding `lang="ts"` to non-TS components seems to help...

For me the issue turned out to be babel config not being used correctly. After digging through the code I found a way to make it work using a somwhat-undocumented...

Seeing the same thing on IntelliJ IDEA version `Build #IU-222.3345.118, built on July 26, 2022`

The problem is that if I intercept the false return value on the call to get(), then you won't be able to store the value false in redis as it...

I see the point @TheLarkInn is making. I guess before going forward in any direction, I would like to understand consensus of what we want `NodeTargetPlugin` to actually do -...

> @vetruvet > > > specify latest Node.js builtins as externals regardless of what version webpack is running on > > This +1 Given that, we can't really use `is-core-module`...

That works, thanks. I can't promise any timing but I will try to whip something up. If someone else can get to it sooner, more power to them!

No, I don't know enough about Jest internals to suggest a fix. ~Besides, I'd expect that a certain multi-billion-dollar corporation would be maintaining this. Don't get me wrong, I'm all...

TIL, thanks for pointing that out. I did end up doing some digging, and while I'm not any closer to finding the root cause, I did notice [this](https://github.com/facebook/jest/blob/eca83e7221137785d585215f9ae9251adcdbacc3/packages/jest-mock/src/index.ts#L1410): ``` resetAllMocks():...

29.4.3 fixes the original issue for me, along with the "Maximum Call Stack Size Exceeded" error. Thanks all!