Reinier Kaper

RC11 also still has this issue, repro: https://stackblitz.com/edit/github-1wqbue-fxk6ua

There's a warning in the docs saying this won't work (for the import part): https://v3.nuxtjs.org/guide/directory-structure/components#client-components The rest of the issue seems a valid problem

Just wanting to add that this is quite a crucial feature to have, because right now we can't run component tests in nuxt3. Vitest also doesn't know about the magic...

Yeah I understand it from a simplicity POV! The hard part is that if you have to trap _every_ call to Graph, it becomes a bit unwieldy. I know JWT...

This solution works, but I think it would be cleaner if there was a native alternative. How about something like: ```vue const { data, error, refresh, pending } = await...

I have a Stackblitz example of major version collisions here: https://stackblitz.com/edit/github-1wqbue-kp7mfb?file=composables%2FuseMain.ts,app.vue,package.json Ignore the dev mode, just step out of it and run `npm run build && npm run preview` to...

I have the same issue. It also ignores "normal" CSS completions like "color".

Still the same type: `chainId: number;` in `index.d.ts` Package version: `"version": "1.7.8",`

I'm using a composable for this: ```js import { ref } from 'vue' const rendererRef = ref() export default function useRenderer () { return { rendererRef, } } ``` in...

Then why does it throw an exception saying that another element is in the way? Wouldn't that automatically mean there's some way to detect it?