` 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_",[3040],{"name":3041,"color":3042},"馃嵃 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.6799838,{"description":3049,"labels":3050,"number":3057,"owner":3030,"repository":3030,"state":3032,"title":3058,"updated_at":3059,"url":3060,"score":3061},"### Environment\n\n#### My machine:\n- Operating System: Windows_NT\n- Node Version: v20.16.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.3\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n\n#### CodeSandbox reproduction:\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.10.1\n- CLI Version: 3.10.0\n- Nitro Version: 2.8.1\n- Package Manager: npm@10.5.0\n- Builder: -\n- User Config: devtools\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nDemo: https://codesandbox.io/p/devbox/2n7n2z\n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003Cmain />\n \u003CTeleport defer to=\"main\">\n \u003CNuxtLayout>\n \u003CNuxtPage />\n \u003C/NuxtLayout>\n \u003C/Teleport>\n \u003C/div>\n\u003C/template>\n```\n\n### Describe the bug\n\nUsing the \u003CNuxtLayout> component within a deferred Teleport consistently throws the following warning in the console:\n\n```\n WARN [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.\n```\n\nThis does not occur if the Teleport is not deferred, but I need to defer it for my use case. It also does not occur if `ssr: false` is specified, so I assume the `app:rendered` and `app:suspense:resolve` hooks are probably [relevant](https://github.com/nuxt/nuxt/blob/edc299a04344897ac110aca3b3a2c2705b0cef35/packages/nuxt/src/pages/runtime/plugins/check-if-page-unused.ts#L22). \n\nVue lets me suppress the inevitable hydration mismatch warning with `\u003Cmain data-allow-mismatch=\"children\" />`, but Nuxt does not let me suppress the warning, so it clutters the console.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3051,3054],{"name":3052,"color":3053},"pending triage","E99695",{"name":3055,"color":3056},"dx","C39D69",30001,"\u003CNuxtLayout> within \u003CTeleport defer> throws warning: \"Your project has pages but the \u003CNuxtPage /> component is not being used\"","2024-11-27T15:13:13Z","https://github.com/nuxt/nuxt/issues/30001",0.6913294,{"description":3063,"labels":3064,"number":3067,"owner":3030,"repository":3031,"state":3068,"title":3024,"updated_at":3069,"url":3070,"score":3071},"The development is ongoing on the default branch of this repository: https://github.com/nuxt/ui.\n\n---\n\nA lot has changed since `@nuxt/ui` was made open-source (May 2023), so the plan here is to rewrite every component from scratch alongside their config.\n\nI'll post regular updates on this issue and on https://twitter.com/benjamincanac.\n\n## Documentation\n\nhttps://ui3.nuxt.dev\n\n## Roadmap (Nov 20, 2024)\n\n- [x] Finish the migration to `reka-ui@alpha` on `@nuxt/ui` & `@nuxt/ui-pro` #2448\n- [x] Write the docs for implemented `@nuxt/ui-pro` components\n- [x] Finish `@nuxt/ui-pro` components\n- [x] Make Nuxt UI Pro v3 work with Vue like Nuxt UI https://github.com/nuxt/ui-pro/pull/742\n- [ ] Implement new components in `@nuxt/ui` like\n - [x] `Calendar` #2618\n - [ ] `InputDate` #2524\n - [x] `Tree` #3180\n - [x] `Stepper` #2733\n- [x] Migrate all the Nuxt UI Pro templates\n - [x] Starter\n - [x] Landing\n - [x] Docs\n - [x] SaaS https://github.com/nuxt-ui-pro/saas/pull/86\n - [x] Dashboard https://github.com/nuxt-ui-pro/dashboard/pull/86\n- [ ] Build the Nuxt UI docs marketing pages\n - [x] Landing\n - [x] Figma\n - [x] Pro -> Landing\n - [x] Pro -> Pricing\n - [x] Pro -> Templates\n - [x] Pro -> Activate\n - [ ] Releases\n- [x] Write migration guide https://ui3.nuxt.dev/getting-started/migration\n- [x] Release `@nuxt/ui` & `@nuxt/ui-pro` officially once `tailwindcss` and `reka-ui` are released\n- [x] Migrate all the Nuxt apps (nuxt.com, image.nuxt.com, eslint.nuxt.com, devtools.nuxt.com, fonts.nuxt.com, hub.nuxt.com, nuxt.studio, etc.)\n- [ ] Implement new `@nuxt/ui` & `@nuxt/ui-pro` components\n- [ ] Create new templates like Changelog, Portfolio, etc. \n\n## Breaking Changes\n\nThe biggest change is the switch to `tailwind-variants`, this will cause lots of breaking changes if you've used the `ui` prop or `app.config.ts` to override the config. I apologize in advance for this but I strongly believe this will be beneficial and will bring consistency across all components.\n\n> At the beginning the config was split in many keys for the same div to give more flexibility, but since then we introduced `tailwind-merge` which now allows us to group those keys together, this is a good opportunity to clean the whole thing. \n\nThe config will now have a `slots` amongst other keys that will specifically target dom nodes. The `ui` prop will only allow you to target those slots.\n\nThese changes alongside the refactor of all components will also improve the types, the `app.config.ts` and `ui` props are now perfectly typed, as well as all components `props`, `slots`, `emits` and `expose`.\n\n> Feel free to comment on this if you have any ideas for the next major.\n\n```[tasklist]\n### Components\n- [x] Accordion\n- [x] Alert\n- [x] Avatar\n- [x] AvatarGroup\n- [x] Badge\n- [x] Breadcrumb\n- [x] Button\n- [x] ButtonGroup\n- [x] Card\n- [x] Carousel\n- [x] Checkbox\n- [x] Chip\n- [x] Collapsible\n- [x] CommandPalette\n- [x] Container\n- [x] ContextMenu\n- [x] Drawer\n- [x] DropdownMenu (Dropdown)\n- [x] Form\n- [x] FormField (FormGroup)\n- [x] Icon\n- [x] Input\n- [x] InputMenu\n- [x] Kbd\n- [x] Link\n- [x] Modal\n- [x] NavigationMenu (HorizontalNavigation/VerticalNavigation)\n- [x] Pagination\n- [x] Popover\n- [x] Progress\n- [x] Provider\n- [x] RadioGroup\n- [x] Select\n- [x] SelectMenu\n- [x] Separator (Divider)\n- [x] Skeleton\n- [x] Slideover\n- [x] Slider (Range)\n- [x] Table\n- [x] Tabs\n- [x] Textarea\n- [x] Toast (Notification)\n- [x] Switch (Toggle)\n- [x] Tooltip\n```\n",[3065],{"name":3066,"color":3025},"release",1289,"closed","2025-07-17T12:55:11Z","https://github.com/nuxt/ui/issues/1289",0.686844,{"labels":3073,"number":3078,"owner":3030,"repository":3030,"state":3068,"title":3079,"updated_at":3080,"url":3081,"score":3082},[3074,3077],{"name":3075,"color":3076},"3.x","29bc7f",{"name":3052,"color":3053},13285,"Page layout not working as intended","2023-01-19T16:51:10Z","https://github.com/nuxt/nuxt/issues/13285",0.6908729,{"description":3084,"labels":3085,"number":3090,"owner":3030,"repository":3030,"state":3068,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v18.20.7`\n- Nuxt Version: `3.15.4`\n- CLI Version: `3.21.1`\n- Nitro Version: `2.10.4`\n- Package Manager: `pnpm@9.14.2`\n- Builder: `-`\n- User Config: `app`, `ssr`, `compatibilityDate`, `devtools`, `modules`, `css`, `runtimeConfig`, `nitro`, `vite`\n- Runtime Modules: `@nuxt/eslint@1.1.0`, `@nuxtjs/tailwindcss@6.13.1`, `@pinia/nuxt@0.10.1`, `@nuxt/image@1.9.0`, `nuxt-swiper@2.0.0`\n- Build Modules: `-`\n\n### Reproduction\n\n- Execute nuxt generate\n- Go to output folder\n- Open index.html file using browser without security\n- 404 page not found \n\n### Describe the bug\n\nHi,\n\nWe are working in nuxt project and we need to develop an static app without nodeJS app server. \n\nIf we use app.vue component all it's working ok but when we create pages folder we receive page not found error to manage different routes with vue-router\n\nWe try to configure prerender routes with nitro but it is not working. \n\nPlease, could you help me? \n\nThank you\n\n### Additional context\n\nWe are using the following nuxt configuration:\n\n```\nimport legacy from '@vitejs/plugin-legacy';\n\nexport default defineNuxtConfig({\n app: {\n cdnURL: './',\n },\n ssr: false,\n compatibilityDate: '2024-11-01',\n devtools: { enabled: false },\n modules: ['@nuxt/eslint', '@nuxtjs/tailwindcss', '@pinia/nuxt', '@nuxt/image', 'nuxt-swiper'],\n css: ['~/assets/css/main.css'],\n runtimeConfig: {\n public: {\n apiBase: process.env.API_BASE_URL,\n authorization: process.env.AUTH_TOKEN,\n },\n },\n vite: {\n plugins: [legacy()],\n },\n});```\n\nThis is the following project structure\n\n\n\n### Logs\n\n```shell-script\nBrk9iX9n.js:9599 [nuxt] error caught during app initialization H3Error: Page not found: /C:/Users/Documents/workspace/nuxt-project/.output/public/index.html\n at createError$1 (Brk9iX9n.js:10488:15)\n at Brk9iX9n.js:14599:54\n at fn (Brk9iX9n.js:9683:20)\n at Object.runWithContext (Brk9iX9n.js:4306:18)\n at callWithNuxt (Brk9iX9n.js:9687:24)\n at Brk9iX9n.js:9533:41\n at EffectScope.run (Brk9iX9n.js:280:16)\n at Object.runWithContext (Brk9iX9n.js:9533:31)\n at Brk9iX9n.js:14599:23\n at Brk9iX9n.js:14028:64\n```",[3086,3087],{"name":3052,"color":3053},{"name":3088,"color":3089},"needs reproduction","FBCA04",31203,"Static pages not working on nuxt 3 project","2025-03-05T19:47:06Z","https://github.com/nuxt/nuxt/issues/31203",0.6920342,{"description":3096,"labels":3097,"number":3100,"owner":3030,"repository":3030,"state":3068,"title":3101,"updated_at":3102,"url":3103,"score":3104},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.4.0\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: modules\r\n- Runtime Modules: ./modules/test-module\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-hcx5za\n\n### Describe the bug\n\nIf `pages/` directory is not created or is empty and all of the pages are defined using `extendPages` in module, it throws warning:\r\n\r\n`Create a Vue component in the pages/ directory to enable \u003CNuxtPage>`\r\n\r\nand shows blank page.\r\n\r\nIf you create e.g. `pages/test.vue`, warning goes away and displays the intended page.\n\n### Additional context\n\nAlso this warning goes away, if I create `app/router.options.ts` file.\n\n### Logs\n\n_No response_",[3098,3099],{"name":3075,"color":3076},{"name":3052,"color":3053},20801,"\u003CNuxtPage> info message does not look up for module pages","2023-05-15T12:47:31Z","https://github.com/nuxt/nuxt/issues/20801",0.69362694,{"description":3106,"labels":3107,"number":3111,"owner":3030,"repository":3031,"state":3068,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### 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:)",[3108],{"name":3109,"color":3110},"question","d876e3",4062,"Can Nuxt UI Pro be used just with Vue, Without Nuxt ?","2025-05-04T17:27:57Z","https://github.com/nuxt/ui/issues/4062",0.6937688,{"description":3117,"labels":3118,"number":3123,"owner":3030,"repository":3031,"state":3068,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, devtools, compatibilityDate, future, css\n- Runtime Modules: @nuxt/ui@3.1.1\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/boring-mirzakhani-vjc9wr\n\n### Description\n\nI have a slideover that is opened with `overlay.open` as per documentation. The slideover uses injected values.\n\nIf the injected value is injected in a component that has `UApp` in template, the injection works. If, on the other hand, the injection is done in a component that does not have `UApp` in template, the injection is lost. Workaround would be to add `UApp` to all components doing injections, but there should only be one `UApp`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3119,3122],{"name":3120,"color":3121},"bug","d73a4a",{"name":3024,"color":3025},4209,"Injections from elsewhere than `UApp` pages do not work on overlay components","2025-06-01T13:00:59Z","https://github.com/nuxt/ui/issues/4209",0.6949583,{"description":3129,"labels":3130,"number":3133,"owner":3030,"repository":3030,"state":3068,"title":3134,"updated_at":3135,"url":3136,"score":3137},"### Environment\n\nNuxi 3.5.2\r\nNuxt project info:\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v16.20.0\r\n- Nuxt Version: 3.5.2\r\n- Nitro Version: 2.4.1\r\n- Package Manager: npm@9.6.7\r\n- Builder: vite\r\n- User Config: modules\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.7.0, @vueuse/nuxt@10.1.2\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://github.com/Archetipo95/nuxt-error-layout\n\n### Describe the bug\n\nI encountered a bug while customizing the error page in the Nuxt framework. The issue results in a hydration mismatch error and component duplication. I have created a minimal reproduction, where accessing a non-existent page triggers a warning in the console (/asd).\r\n\r\nPlease let me know if you need additional information. I appreciate your prompt attention to this matter.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3131,3132],{"name":3075,"color":3076},{"name":3052,"color":3053},21385,"Hydration mismatch in error page with NuxtLayout (component duplication)","2023-07-23T11:56:03Z","https://github.com/nuxt/nuxt/issues/21385",0.6960272,["Reactive",3139],{},["Set"],["ShallowReactive",3142],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMG3OXXfYFwidX_UbQET3EZ-_QVxnklkCGJ0Zw163XH8":-1},"/nuxt/ui/4603"]