Summary
add compatibility with new Nuxt unrouting
Motivation
Nuxt 4.4 migrated its page scanner to the new unrouting library (and bumped to vue-router v5).
It looks like unrouting treats Foo@viewName.vue as a vue-router NAMED VIEW attached to the same route as Foo.vue rather than emitting a separate route whose path contains @viewName. Named-view files therefore land in route.components[viewName], and Nuxt itself doesn't forward components into routes.mjs, leaving the file orphaned.
Just wanted to ask if there is a plan to cover those?
Proposed Solution
No response
Would you like to work on this new feature?
Summary
add compatibility with new Nuxt unrouting
Motivation
Nuxt 4.4 migrated its page scanner to the new unrouting library (and bumped to vue-router v5).
It looks like unrouting treats
Foo@viewName.vueas a vue-router NAMED VIEW attached to the same route asFoo.vuerather than emitting a separate route whose path contains@viewName. Named-view files therefore land inroute.components[viewName], and Nuxt itself doesn't forwardcomponentsintoroutes.mjs, leaving the file orphaned.Just wanted to ask if there is a plan to cover those?
Proposed Solution
No response
Would you like to work on this new feature?