Matthew Hintzke

@kind-serge I assumed it was a known issue but just wanted to confirm so thanks! The issue definitely makes sense and the workaround is easy enough to mitigate the problems...

I am also having this issue trying to use Node v20 and `NodeNext` `module` and `moduleResolution` values. I have tried a few combinations and couldn't get it to build unless...

@igordanchenko I appreciate the insight! I will preface that I am in the middle of upgrading a large project from Node v10 and associated packages to Node v22 so a...

@igordanchenko Here is my setup: `package.json`  `tsconfig.json`  `vite.config.ts`  I only have a single explicitly `import` of `vitest`. The rest are all to `vitest-mock-extended` whicih provides utilities for...

@igordanchenko Yes, can confirm.  I will start to do that and see how it goes. Thanks

@igordanchenko Here is my reproduction. It definitely seems related to using `vitest-mock-extended` as once I added it and imported `mock` it blew up. I will go over to that package...

@softcraft-development are you using `vitest-mock-extended` by chance? My above stackblitz reproduces the issue by simply utilizing that library in any form. I created https://github.com/eratio08/vitest-mock-extended/issues/546 to hopefully get it looked at...

@igordanchenko oooh I did not even notice that yet. Good catch and cool tool there. I guess we will just see what they say, but this is definitely not a...

@igordanchenko ah, yes after re-reading it with new found knowledge I see what his issue was. You are correct, this should probably be closed

@andyleejordan The callstack and more pertinent information is in the forked repository README.md I linked above. Here it is though just to make it easier: ```csharp Uncaught Error: Internal Error...