Kael
Kael
The types actually already work like this: ```ts const router = new Hono() .use(async (c, next) => { c.set('test', 'override') await next() }) const app = new Hono() .use(async (c,...
This belongs on vuejs/core, they don't seem to have any interest in first-class jsx support though. I had to write my own defineComponent to get slot types to work: https://github.com/vuetifyjs/vuetify/blob/327a2c92404b1cb7faba68c3655550ca6f574d25/packages/vuetify/src/util/defineComponent.tsx#L214-L243...
Another one from #21300, this is extremely similar to #21551
https://github.com/vuetifyjs/vuetify/issues/21392#issuecomment-2865205230
Weird how inconsistent it is, for me it closes if I click on anything but 12-23. If you're handling closing the menu yourself it should have `:close-on-content-click="false"`, but the time...
https://vitejs.dev/guide/api-plugin.html#virtual-modules-convention I guess nuxt is handling those wrong? With just vite the url is `/@id/__x00__plugin-vuetify:styles/main.sass` And also probably not related to this.
Well yeah `styles: "sass"` doesn't use virtual modules. Again, unrelated to this issue.
There's two things going on here, not sure if they're related. - Sourcemap warnings are supposed to be hidden for modules starting with `\0` (https://github.com/nuxt/nuxt/issues/14124) - Something in nuxt is...
This has already been changed: 7c8aeefdc097ff9b74a733ed17b6a8cd9e1f8575 Please try the latest nightly build: https://vuetifyjs.com/en/getting-started/installation/#nightly-builds