Daniel Roe
Daniel Roe
It would be a good idea to add a type test to this repo if this is occurring, to ensure it doesn't happen in future. I suspect the issue is...
At runtime, you can customise the routes used to initialise Vue router with a router options file: https://nuxt.com/docs/guide/recipes/custom-routing#using-approuteroptions. That would enable you to override the file based routing entirely based...
good point! I would fully advise migrating to nuxt fonts
Did you have a look at the test failures? `/keepalive/keepalive-in-nuxtpage-2/_payload.json?dev` is returning HTML rather than JSON.
why do we need an event system? i don't believe any communication is required, just updating the rules in a context object passed to the plugin
Here's a minimal reproduction (just `vue` + `vue-tsc`) showing the issue: https://stackblitz.com/edit/stackblitz-starters-zu6gov To be clear, this issue is only reproducible with `strict: false`. It's not reproducible on the SFC playground...
if we fail gracefully, that should be good enough, right?
No longer reproducible in v3.15.3
yes, exactly. you can ignore the warning for now, and we'll guard this to avoid accessing the key on client-side
You can do this by adding additional folders to the `components.dirs` array in your `nuxt.config`, e.g.: ```ts export default defineNuxtConfig({ components: { dirs: [ '~/components/(2024)', '~/components/(2023)', '~/components', ], }, })...