zumm

@logaretm Probably this is happening because of incorrect typed `vuetifyConfig` (we can see on the screenshot author is using it) ```ts import * as yup from 'yup'; import { useForm,...

And there is another issue with `defineField` typing. It defines type of object fields as `PartialObjectDeep | undefined` so they can't be used with components which expect `T` as model....

Seems like enabled `compilerOptions.composite` option in my `tsconfig.json` file causes this issue. I guess it was enabled by old `vue@create` template. There is no such option in newest template, so...

@mrlubos I think this issue isn't relevant to `openapi-ts` itself, just consequence of weird interaction between pnpm and typescript. But if you want to investigate this issue a bit farther...

I'm facing same problem in my nuxt project. [Forcing transpile](https://dev.to/jeanjavi/solving-uncaught-in-promise-referenceerror-exports-is-not-defined-in-nuxtjs-with-vee-validate-1lf9) for `vee-validate` package solves the problem.

Any updates? This problem is even worse because server and client handle cookie in different ways. Server uses only root path cookie, client uses current path cookie. It leads to...

@Coops0 My current solution is a way simpler. I just monkey patched this package. :) Thanks to `pnpm patch`. ```js window.document.cookie = storageKey + "=" + preference + "; path=/";...

> happy to open a pr [@zumm](https://github.com/zumm) ? Shouldn't it be fixed by https://github.com/nuxt-modules/color-mode/pull/301 ?

I can confirm this feature is really important. Actually it is near impossible for me to use tanstack plugin cuz almost every param is ref/computed.

I wanna share workaround i found recently. `useQuery` (and others `vue-query` composables) accepts reactive objects as options. So you can do things like that: ```ts const somethingId = ref(23) const...