Daniel Roe
Daniel Roe
Here's the result from the [Twitter poll](https://x.com/danielcroe/status/1828710815974752608):  I would observe that we're polling users who already know about devtools and in many cases are...
I would be happy for that to apply to all users of devtools, unless you think it's a breaking behaviour change
Would you see if you can reproduce this in pure Nitro ([reproduction sandbox](https://stackblitz.com/github/unjs/nitro/tree/main/examples/hello-world)), and if so, raise [there](https://github.com/unjs/nitro/issues/new/choose)? 🙏
This doesn't seem to be related to `future.compatibilityVersion`. Did you have a version of Nuxt + vue-router that behaves as you expect? updated repro to show same behaviour on previous...
possibly related: https://github.com/vitejs/vite/pull/17938 is it resolved with latest vite?
Can you reproduce with just Vite (without Nuxt)?
For now, this is a workaround you can use: ```ts export default defineNuxtConfig({ hooks: { 'vite:extendConfig' (viteInlineConfig, env) { if (env.isClient) { const importPlugin = viteInlineConfig.plugins?.find(p => p && 'name'...
seems it wasn't a nuxt issue: https://github.com/nodejs/node/issues/54590#issuecomment-2312241251
We won't be able to support the full breadth of `vue-router`'s pattern matching, but we should be able to do this for at least some route patterns, which could be...
Would you see if you can raise upstream at https://github.com/unjs/giget? 🙏