Ragura

I seem to be encountering a devtool related issue with Pinia. I defined a new store using the composition API method (not the object store format) and when directly modifying...

Thanks @kamilglod for the excellent workaround. There's still the issue of the `@factory.post_generation` decorated functions thinking the first parameter of the function is the factory instance and not an instance...

Any updates on this? We have embraced Suspense and async components very heavily in our project and this is really holding us back in writing tests. I've noticed it's the...

This happens to me to, within a pnpm workspace. I set the launch.json program path to the `vitest.mjs` of the app's node_modules folder, which runs the command correctly, but I...

Encountering the same issue with `9.2.2`. I can provide a little more information. I am writing my localization files in `.yml` format and importing the messages from the virtual `@intlify/vite-plugin-vue-i18n/messages`....

I'm getting the same errors in my own mono repo when using the extension. I can see the tests, but not run them (get the same "Test result not found"...

Have the same issue as well, working in a multi-root VSCode workspace. I've tried variations of the command (`npx vitest`, `pnpm test --`, ... It's important to note that in...

Also having the same issue with the same error message upon opening PyCharm 2023.1. Using a M1 mac, latest os.

Have the same problem when using `$fetch`. Strangely I can't seem to reproduce it in a minimal reproduction, so it might have something to do with a large return type...

This issue is still present. The workaround of providing a type to `$fetch()`, like `$fetch()` works, but of course this isn't ideal because we lose automatic type inference. This seems...