` 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_",[2861],{"name":2862,"color":2863},"馃嵃 p2-nice-to-have","0E8A16",25912,"nuxt","open","\"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.6329533,{"description":2872,"labels":2873,"number":2880,"owner":2865,"repository":2865,"state":2881,"title":2882,"updated_at":2883,"url":2884,"score":2885},"### Environment\n\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.0.0-rc.10`\r\n- Nitro Version: `0.5.3`\r\n- Package Manager: `npm@8.15.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-l5dwjy\n\n### Describe the bug\n\nI used the built in component Teleport in my project and everything was working fine or that's what I thought,\r\nit was working ok because i have v-if on the Teleport component, once I moved the v-if to the slot element i got this error\r\n\r\n`[Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at`\r\n`Uncaught (in promise) TypeError: Cannot read properties of null (reading 'insertBefore')`\r\n\r\nand because my project is not small i thought maby i made a mistake somewhere caused this to happen so i tried to make reproduction with a fresh nuxt install then i got Hydration node mismatch when using Teleport to the layout\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2874,2877],{"name":2875,"color":2876},"3.x","29bc7f",{"name":2878,"color":2879},"pending triage","E99695",14967,"closed","Hydration mismatch when using Teleport","2023-01-19T17:43:08Z","https://github.com/nuxt/nuxt/issues/14967",0.65318173,{"description":2887,"labels":2888,"number":2894,"owner":2865,"repository":2865,"state":2881,"title":2895,"updated_at":2896,"url":2897,"score":2898},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v21.5.0`\r\n- Nuxt Version: `3.10.0`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `npm@10.2.4`\r\n- Builder: `-`\r\n- User Config: `devtools`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\nBut I believe this bug happens in all environments.\r\n\r\n### Reproduction\r\n\r\nOriginal reproduction by @robert-gruner\r\nhttps://stackblitz.com/~/edit/github-wgg4gm-sdfzwd\r\n\r\nMinimal reproduction by me\r\nhttps://stackblitz.com/edit/github-wgg4gm-8hhehw\r\n\r\n### Describe the bug\r\n\r\nThis issue is an edge case which was not tested in #25490.\r\n\r\nWith the `content.global.ts`, which dynamically changes layout, the warning message is always shown.\r\nWithout the middleware (i.e. without calling `setPageLayout`), the warning message is shown expectedly.\r\n\r\n### Additional context\r\n\r\nThis issue and the reproduction were originally reported by @robert-gruner as https://github.com/nuxt/nuxt/pull/25490#issuecomment-1925902990.\r\n\r\n### Logs\r\n\r\n_No response_",[2889,2890,2891],{"name":2875,"color":2876},{"name":2878,"color":2879},{"name":2892,"color":2893},"dx","C39D69",25617,"Warning for `NuxtPage` absence is always shown if `setPageLayout` is called in middleware","2024-02-05T13:51:26Z","https://github.com/nuxt/nuxt/issues/25617",0.65787256,{"description":2900,"labels":2901,"number":2904,"owner":2865,"repository":2865,"state":2881,"title":2905,"updated_at":2906,"url":2907,"score":2908},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.0.0-rc.12`\r\n- Nitro Version: `0.6.0`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `nitro`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nsee https://github.com/chrisnoden/nuxt3-bug\r\n\r\nCreate a couple of layouts, choose one of them using the code example from https://v3.nuxtjs.org/guide/directory-structure/layouts#changing-the-layout-dynamically \r\n\r\neg:\r\n```\r\ndefinePageMeta({\r\n layout: false,\r\n});\r\nsetPageLayout('minimal');\r\n```\n\n### Describe the bug\n\nYou get 2 warnings that do appear to be definitely unwanted.\r\n\r\n1. a Vue warn about `Hydration mode mismatch` implying the SSR render differs from the browser render.\r\n2. a nuxt warn that your chosen layout \"does not have a single root node...\" when it does.\r\n\r\nThis bug does not appear if you are able to use one of the other methods to change layout.\n\n### Additional context\n\nThe chosen layout DOES get used, but the warnings are reasonably concerning\n\n### Logs\n\n_No response_",[2902,2903],{"name":2875,"color":2876},{"name":2878,"color":2879},15297,"setPageLayout causes hydration mode mismatch and nuxt warning","2023-01-19T17:47:33Z","https://github.com/nuxt/nuxt/issues/15297",0.659539,{"description":2910,"labels":2911,"number":2914,"owner":2865,"repository":2865,"state":2881,"title":2915,"updated_at":2916,"url":2917,"score":2918},"### Environment\r\n\r\nOficial page - https://v3.nuxtjs.org/api/components/nuxt-layout\r\nLocal env is:\r\n> Nuxt 3.0.0-rc.12 with Nitro 0.6.0\r\n\r\n### Reproduction\r\n\r\nhttps://v3.nuxtjs.org/api/components/nuxt-layout\r\n\r\n### Describe the bug\r\n\r\nApp.vue have issue on declared way to use layouts:\r\n\r\n> You can use \u003CNuxtLayout /> component to activate default layout on **_app.vue_** or error.vue.\r\n\r\nAnd in app get this message: \r\n\r\n` WARN Using \u003CNuxtLayout> inside app.vue will cause unwanted layout shifting in your application.Consider removing \u003CNuxtLayout> from app.vue and using it in your pages.`\r\n\r\n\r\n### Additional context\r\n\r\n`App.vue`\r\n```js\r\n\u003Ctemplate>\r\n \u003CNuxtLayout>\r\n \u003CNuxtPage />\r\n \u003C/NuxtLayout>\r\n\u003C/template>\r\n```\r\n\r\n### Logs\r\n\r\n_No response_",[2912,2913],{"name":2875,"color":2876},{"name":2878,"color":2879},15240,"[DOCS] NuxtLayout warn vs documentation","2024-11-08T01:59:31Z","https://github.com/nuxt/nuxt/issues/15240",0.66413677,{"description":2920,"labels":2921,"number":2928,"owner":2865,"repository":2865,"state":2881,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-issues-25196\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003CClientOnly>\r\n \u003CNuxtLayout>\r\n \u003CNuxtPage />\r\n \u003C/NuxtLayout>\r\n \u003C/ClientOnly>\r\n\u003C/template>\r\n```\r\n\r\n### Describe the bug\r\n\r\nWhen using a `\u003CClientOnly>` component around the `App.vue` (only SSR the app shell), the NuxtLayout warning will appear even though the component is used.\r\n\r\n### Additional context\r\n\r\nRelated: https://github.com/nuxt/nuxt/issues/24912\r\n\r\n### Logs\r\n\r\n_No response_",[2922,2923,2924,2927],{"name":2875,"color":2876},{"name":2892,"color":2893},{"name":2925,"color":2926},"bug","d73a4a",{"name":2862,"color":2863},25196,"`\u003CNuxtLayout /> component has not been used.` Warning when using `\u003CClientOnly>` in `app.vue`","2024-02-09T20:33:36Z","https://github.com/nuxt/nuxt/issues/25196",0.66417533,{"description":2934,"labels":2935,"number":2937,"owner":2865,"repository":2865,"state":2881,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.3\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-pjcxjvhm?file=app.vue,pages/index.vue\n\n### Describe the bug\n\n1. Open the **minimal reproduction**. \n2. Open the browser **devtools**, and you will see a Vue warning: \n\n ```text\n [Vue warn]: Component inside \u003CTransition> renders non-element root node that cannot be animated.\n ```\n\nHowever, in the provided **minimal reproduction**, the `\u003CNuxtPage>` slot contains only a single root node: \n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003CNuxtPage\n :transition=\"{ name: 'fade', mode: 'out-in', appear: true }\"\n #=\"{ Component }\"\n >\n \u003Ccomponent :is=\"Component\" />\n \u003C/NuxtPage>\n \u003C/div>\n\u003C/template>\n```\n\nIf the `\u003CNuxtPage>` slot is not used, the warning does not appear, and everything works as expected. \n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2936],{"name":2878,"color":2879},30806,"`\u003CNuxtPage>` slots not working with transition","2025-02-06T18:10:38Z","https://github.com/nuxt/nuxt/issues/30806",0.66453,{"description":2943,"labels":2944,"number":2949,"owner":2865,"repository":2865,"state":2881,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v18.18.2\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.9.1\r\n- Package Manager: yarn@1.22.21\r\n- Builder: -\r\n- User Config: experimental, app, runtimeConfig, modules, devtools, proxy, vue, vant, plugins, postcss, css, vite\r\n- Runtime Modules: @vueuse/nuxt@9.13.0, @vant/nuxt@1.0.4, nuxt-proxy-request@1.9.0\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-xnrjjn-ttgu7b?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nIn nuxt3, keepalive has different results when using NuxtLayout and not using NuxtLayout.\r\nIf you use pageTransition on nuxt.config.ts or on pages, there will also be a problem that keepalive does not take effect.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_\n```[tasklist]\n### Tasks\n```\n",[2945,2946],{"name":2878,"color":2879},{"name":2947,"color":2948},"pages","00DFB5",26216,"The keepalive attribute of NuxtPage cannot be used normally under the NuxtLayout package","2024-11-29T14:09:43Z","https://github.com/nuxt/nuxt/issues/26216",0.666269,{"description":2955,"labels":2956,"number":2959,"owner":2865,"repository":2865,"state":2881,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.2\r\n- Nitro Version: 2.3.3\r\n- Package Manager: npm@8.6.0\r\n- Builder: vite\r\n- User Config: meta, routeRules, runtimeConfig, pages, css, components, modules, content, i18n\r\n- Runtime Modules: @nuxt/content@2.6.0, @nuxtjs/i18n@8.0.0-beta.11\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nA minimal reproduction is not possible because it requires to update the repo to reproduce.\r\n\r\n### Describe the bug\r\n\r\nWhen developing, every time I make a change, the preview reloads showing a fake `[Vue warn]: Hydration text mismatch`\r\n\r\nIf I stop `nuxi dev`, delete the `/.nuxt` folder and restart `nuxi dev`, the warning disappears. Delete `/.nuxt` is not always necessary, but it is necessary to restart `nuxi dev`.\r\n\r\nWhat I'm actually doing is to ignore the warning and restart as described, before `git commit`, to make sure the warning is fake.\r\n\r\nIt seems to me that the Client is showing as rendering the previous version (before saving the change) and the Server the new one.\r\n\r\nIs this the expected behavior? If so, it's really inconvenient. \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\n[Vue warn]: Hydration text mismatch:\r\n- Client: \"\u003COMITTED>\"\r\n- Server: \"blog\" \r\n at \u003CNuxtLink to=\"\u003COMITTED>\" > \r\n at \u003CMerchantProfile title=\"\u003COMITTED>\" description=\"\u003COMITTED>\" image=\"me.jpg\" ... > \r\n at \u003CBody> \r\n at \u003CHtml lang=\"en-US\" dir=\"ltr\" > \r\n at \u003CDefault > \r\n at \u003CLayoutLoader key=\"default\" name=\"default\" hasTransition=false > \r\n at \u003CFragmentWrapper > \r\n at \u003CNuxtLayout> \r\n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \r\n at \u003CRouteProvider key=\"/\" routeProps= {Component: {鈥, route: {鈥} pageKey=\"/\" ... > \r\n at \u003CFragmentWrapper > \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\n```\r\n```\r\n",[2957,2958],{"name":2875,"color":2876},{"name":2878,"color":2879},20437,"Fake [Vue warn]: Hydration text mismatch with nuxi dev","2023-05-12T16:25:05Z","https://github.com/nuxt/nuxt/issues/20437",0.6671526,{"labels":2965,"number":2968,"owner":2865,"repository":2865,"state":2881,"title":2969,"updated_at":2970,"url":2971,"score":2972},[2966,2967],{"name":2875,"color":2876},{"name":2878,"color":2879},13431,"Throw \"Hydration node mismatch\" error when using teleport","2023-01-19T16:55:42Z","https://github.com/nuxt/nuxt/issues/13431",0.66732574,["Reactive",2974],{},["Set"],["ShallowReactive",2977],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f-DZGFjEGMhBXzh7axq4VZPZyi5Iwf_C52obZAeDrtac":-1},"/nuxt/nuxt/30001"]