Isak ✏ ⇝

Same issue here. Component props are not respected in the autocomplete at the moment.

You can get it running in vue using [veaury](https://github.com/devilwjp/veaury). There are some steps involved. Install necessary packages: `yarn add -D veaury @uniswap/widgets @fontsource-variable/inter vite-plugin-node-polyfills@^0.9.0` ````vue import '@fontsource-variable/inter'; //@ts-ignore import {...

Hi, I'm experiencing the same. I really enjoy strapi, but these properties being marked as nullable makes my typescript experience quite messy. Would love to see a fix on this.

The patch doesn't seem to work on my end, trying to use it with yarns native patch support. It's the module builder that needs to be updated, this patch can't...

> Anyone have it working in nuxt3 yet? Seems like there was an unannounced release of `beta-25` that you can use now! `"@vueuse/motion": "2.0.0-beta.25",` Works fine with nuxt 3.0. 🚀✨

The PR seems to be merged but I'm still getting an issue on howler with Nuxt 3 I'm getting `Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'Howl')`...

I've been seeing the same bug coming up the latest week, fixed it by removing the use of `FloatingMenu` from `@tiptap/vue-3`

> You can change the auto-complete suggestions and code fix (quick fix) with a TypeScript Plugin. A TypeScript Plugin has to be a package (cannot be a local file), so...