` and `\u003CNuxtLayout />` components in the below way:\r\n```vue\r\n \u003Cdiv v-if=\"loading\">loading...\u003C/div>\r\n \u003CNuxtLayout v-else>\r\n \u003CNuxtPage />\r\n \u003C/NuxtLayout>\r\n```\r\n\r\nBut it shows up the below warning in console log.\r\n```\r\n[nuxt] Your project has pages but the `\u003CNuxtPage />` component has not been used. You might be using the `\u003CRouterView />` component instead, which will not work correctly in Nuxt. You can set `pages: false` in `nuxt.config` if you do not wish to use the Nuxt `vue-router` integration.\r\n[nuxt] Your project has layouts but the `\u003CNuxtLayout />` component has not been used.\r\n```\r\n\r\n### Additional context\r\n\r\nMy purpose is fetching some environment data from server before NuxtLayout and NuxtPage rendered and shows a loading layout. In addition, I will use it with SSR off.\r\n\r\n### Logs\r\n\r\n_No response_",[2869],{"name":2870,"color":2871},"🍰 p2-nice-to-have","0E8A16",25912,"\"NuxtPage / NuxtLayout component has not been used\" warn when NuxtLayout async show up","2025-02-21T12:34:45Z","https://github.com/nuxt/nuxt/issues/25912",0.700592,{"description":2878,"labels":2879,"number":2887,"owner":2860,"repository":2860,"state":2861,"title":2888,"updated_at":2889,"url":2890,"score":2891},"Similar approach to https://github.com/antfu/unplugin-vue-components#importing-from-ui-libraries\r\n\r\nI been using this pattern for `unplugin-vue-components` for a while and I think it turns out a flexible and straightforward solution to support various component libraries without the changes need to be done on the author side. For example, some components might use JSX to build up the library, or uses all named exports on the top-level module, or imports styles separately. Additionally, the resolver opens more possibility to integrate on-demand usages, for example `unplugin-icons` which the icons are served virtually via module name. This would also be great if we could join the force from the Vite side to provide a uniformed resolver solution and made it easier for ppl adopting to more libraries at ease.",[2880,2883,2886],{"name":2881,"color":2882},"enhancement","8DEF37",{"name":2884,"color":2885},"good first issue","fbca04",{"name":2870,"color":2871},11785,"Support custom resolvers for @nuxt/components","2024-06-30T11:10:42Z","https://github.com/nuxt/nuxt/issues/11785",0.703365,{"description":2893,"labels":2894,"number":2898,"owner":2860,"repository":2899,"state":2900,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### Description\n\nHi !\nFirst of all great work. I love this Kit.\nBut I was wondering if this Nuxt UI Kit (pro version) can be used just in Vue ? Without having the while framework ?\nI possibly need to build an app with AdonisJS with intertia in front, without haveing front router etc. \nI would just have the Vue templating, and hopefully built thanks to this kit \n:)",[2895],{"name":2896,"color":2897},"question","d876e3",4062,"ui","closed","Can Nuxt UI Pro be used just with Vue, Without Nuxt ?","2025-05-04T17:27:57Z","https://github.com/nuxt/ui/issues/4062",0.678083,{"description":2906,"labels":2907,"number":2911,"owner":2860,"repository":2860,"state":2900,"title":2912,"updated_at":2913,"url":2914,"score":2915},"The problem that im facing has to do with nuxt-link and nuxt-view. As far as i've used vuejs i remember that if you put router-link and down below you put a router-view it will render everything with navigation bar if its there. However with nuxt i put nuxt-link (or router-link for testing) and below i put nuxt-view (or router-view for testing) it redirects me to another page but the navigation bar dissapears. At first i was told that i might need to use layout instead of components but its pretty much the same result. Here is the code:\r\n\r\n \r\n \u003Ctemplate>\r\n \u003Cdiv id=\"\">\r\n \u003Cnuxt-link :to='{name: \"terms-sections-test1\"}'>Go to 1 \u003C/nuxt-link>\r\n \u003Cnuxt-link to='/terms/sections/test2'>Go to 2 \u003C/nuxt-link>\r\n \u003Crouter-link to='terms/sections/test1'>ROUTER LINK\u003C/router-link>\r\n\r\n\r\n \u003Cnuxt-view> \u003C/nuxt-view>\r\n \u003Crouter-view >\u003C/router-view>\r\n\r\n\r\n\r\n \u003C/div>\r\n \u003C/template>\r\n \u003Cscript>\r\n export default {\r\n /* eslint-disable */\r\n layout: 'navigation'\r\n\r\n }\r\n \u003C/script>\r\n \u003Cstyle lang=\"css\" scoped>\r\n \u003C/style>\r\n\r\nIs there a work around so that i dont have to include layout everytime in its children components? or i need to include them everywhere? sorry for the noob question but i cant really see good documentation for nuxt-view.\r\n\r\nP.S: everytime when i press on my first nuxt-link it redirects me to the page but when i go back to initial page (the code above) it gives me this warning:\r\n\r\n [Vue warn]: Unknown custom element: \u003Cnuxt-view> - did you register the component correctly? For \r\n recursive components, make sure to provide the \"name\" option.\r\n\r\nPlease help :)\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c977\">#c977\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2908],{"name":2909,"color":2910},"2.x","d4c5f9",1116,"Nuxt-view with nuxt-link","2023-01-18T15:40:45Z","https://github.com/nuxt/nuxt/issues/1116",0.67898315,{"description":2917,"labels":2918,"number":2923,"owner":2860,"repository":2860,"state":2900,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### Environment\n\nNuxt project info: \r\n\r\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.0.0-rc.11`\r\n- Nitro Version: `0.5.4`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\n\n### Reproduction\n\n- Create a Nuxt module project:\r\n\r\n```\r\nnpx nuxi init -t module my-module\r\ncd my-module\r\nnpm i \r\nnpm run dev:prepare\r\n```\r\n\r\n- Make a call to `extendPages` within `module.ts` to add a page:\r\n\r\n```ts [module.ts]\r\nextendPages((pages) => {\r\n pages.push({\r\n name: 'module-page',\r\n path: '/:slug(.*)*',\r\n // @ts-ignore\r\n file: resolve(runtimeDir, './MyPage.vue')\r\n })\r\n})\r\n```\r\n- Add a page `~/src/runtime/MyPage.vue`:\r\n\r\n```vue [MyPage.vue]\r\n\u003Ctemplate>\r\n \u003Cdiv>Hello!\u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n- Update `app.vue` to add `\u003CNuxtLayout>` and `\u003CNuxtPage>`:\r\n\r\n```vue [app.vue]\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CNuxtLayout>\r\n \u003CNuxtPage />\r\n \u003C/NuxtLayout>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n- Run the project with `npm run dev` and note that the page has not loaded:\r\n```\r\nPlugin by my-module!\r\n√ Vite server hmr 4 files in 50.259ms\r\n[Vue warn]: Failed to resolve component: NuxtPage\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\nPlugin by my-module!\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n√ Vite server hmr 4 files in 143.147ms\r\n[Vue warn]: Failed to resolve component: NuxtPage\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\nPlugin by my-module!\r\n```\n\n### Describe the bug\n\nNuxt cleverly strips out all router functionality if a project does not have a pages directory. However, this functionality is still removed if an installed module calls 'extendPages', so modules can't actually provide pages unless the project itself already has some, which may not always be the case.\r\n\r\nI think router functionality should be preserved by Nuxt if `extendPages` is called.\r\n\n\n### Additional context\n\nI am creating a module which creates a catch all page so I can do my own routing. I don't want to need to create a page in every project in order for my module's page to take effect. I can imagine other modules will want to act similarly, even if they're only providing more specific routes/pages.\n\n### Logs\n\n_No response_",[2919,2922],{"name":2920,"color":2921},"3.x","29bc7f",{"name":2857,"color":2858},15060,"Nuxt does not include router functionality when a module calls extendPages unless the project has its own pages directory","2023-01-19T17:44:18Z","https://github.com/nuxt/nuxt/issues/15060",0.67912686,{"description":2929,"labels":2930,"number":2936,"owner":2860,"repository":2860,"state":2900,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Describe the feature\n\nHello!\n\nI'm currently working on implementing devtools for Nuxt UI (PR: [#2196](https://github.com/nuxt/ui/pull/2196)). As part of this, I need to inject a page within the user's app that allows our devtools to render components based on the user's Nuxt UI configuration.\n\nThe challenge I'm encountering is that I could not find a way to inject this page without inheriting from the user's `app.vue` (using [`extendPages`](https://nuxt.com/docs/api/kit/pages#extendpages)) , which could cause unintended side effects.\n\nTo address this, I thought we could introduce a way to inject pages without inheriting from `app.vue`, similar to what’s done in for the [test utils](https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/app/components/nuxt-root.vue#L43), by rendering the nuxt page directly if it matches a specific condition.\n\n### Additional information\n\n- [x] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2931,2932,2935],{"name":2881,"color":2882},{"name":2933,"color":2934},"discussion","538de2",{"name":2857,"color":2858},29365,"Allow injecting pages without inheriting from `app.vue`","2025-02-23T10:08:58Z","https://github.com/nuxt/nuxt/issues/29365",0.6834971,{"labels":2942,"number":2945,"owner":2860,"repository":2860,"state":2900,"title":2946,"updated_at":2947,"url":2948,"score":2949},[2943,2944],{"name":2881,"color":2882},{"name":2920,"color":2921},13322,"provide universal route handling utilities","2023-01-19T16:52:31Z","https://github.com/nuxt/nuxt/issues/13322",0.6860592,{"description":2951,"labels":2952,"number":2956,"owner":2860,"repository":2860,"state":2900,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Describe the feature\n\nhey 👋\r\n\r\nrecently I came across a special case where I had to pass a component to child NuxtPage and figured out that NuxtPage does not seem to support passing vslot.\r\n\r\nHere is the documentation from Vue Router about that:\r\nhttps://router.vuejs.org/guide/advanced/router-view-slot\r\n\r\nSeems very useful functionality. Do you think it would be possible to support it with NuxtPage?\r\n\r\nCheers!\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2953,2954,2955],{"name":2881,"color":2882},{"name":2920,"color":2921},{"name":2870,"color":2871},26998,"RouterView slot","2024-05-03T12:58:19Z","https://github.com/nuxt/nuxt/issues/26998",0.68619746,{"description":2962,"labels":2963,"number":2968,"owner":2860,"repository":2899,"state":2900,"title":2969,"updated_at":2970,"url":2971,"score":2972},"### Description\n\nWith Nuxt UI 3.02, configured for Vue, I was able to use it without vue-router. It now fails with 3.1 if it is not installed. I am in a slightly odd environment, in which I am using Astro with Vue client islands and Nuxt UI- so I understand this config is probably not supported. But, it was working with 3.02...just wondering if this is now required for 3.1 moving forward.\n\nOddly, it continues to work for any existing project, upgraded to 3.1. Its only on a new project or if an existing project is rebuilt (node_modules and lock file deleted) does it fail:\n\n[ERROR] Could not resolve \"vue-router\" imported by \"@nuxt/ui\". Is it installed?\n\nI scanned through the release notes and nothing jumped out regarding vue-router - so my apologies if it is mentioned there and I overlooked it.\n\nThanks.",[2964,2965],{"name":2896,"color":2897},{"name":2966,"color":2967},"v3","49DCB8",4038,"Does Nuxt UI 3.1 (configured for Vue) now require vue-router?","2025-05-02T17:17:41Z","https://github.com/nuxt/ui/issues/4038",0.68871516,["Reactive",2974],{},["Set"],["ShallowReactive",2977],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fk7OuCck3daV2qqNYMF7jZwcAQz3QildTs2GLEGnpD5I":-1},"/nuxt/ui/4233"]