\n\n3) Navigate to `pages/index.vue`, modify the `console.log()` and save\n\n### Describe the bug\n\nThe previous [issue](https://github.com/nuxt/nuxt/issues/25214) was closed, but the error remains even in the latest Nuxt version.\n\nThe error will disappear if you add `lazy:true` option\n\n```\nconst { data } = await useFetch('https://jsonplaceholder.typicode.com/todos/1', {\n lazy: true\n})\n```\n\nAs you can see, both `app.vue` `layouts/default.vue` are wrapped with `divs` as it was suggested in the previous issue but we still get the bug.\n\nIs adding `lazy` option is the best workaround as for now?\n\n\u003Cimg width=\"500\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ca5929e7-f84b-4d0f-a57b-e1cf38c34813\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nvirtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:16 [Vue warn]: Unhandled error during execution of component update \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage> \n at \u003CDefault ref=Ref\u003C Proxy(Object)聽{鈥 > > \n at \u003CAsyncComponentWrapper ref=Ref\u003C Proxy(Object)聽{鈥 > > \n at \u003CLayoutLoader key=\"default\" layoutProps= {ref: RefImpl} name=\"default\" > \n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"default\" name=\"default\" ... > \n at \u003CNuxtLayout> \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\nwarn$1 @ runtime-core.esm-bundler.js:51\nlogError @ runtime-core.esm-bundler.js:263\nhandleError @ runtime-core.esm-bundler.js:255\ncallWithErrorHandling @ runtime-core.esm-bundler.js:201\nflushJobs @ runtime-core.esm-bundler.js:408\nPromise.then\nqueueFlush @ runtime-core.esm-bundler.js:322\nqueueJob @ runtime-core.esm-bundler.js:317\neffect2.scheduler @ runtime-core.esm-bundler.js:5448\ntrigger @ reactivity.esm-bundler.js:253\nendBatch @ reactivity.esm-bundler.js:311\nnotify @ reactivity.esm-bundler.js:597\ntrigger @ reactivity.esm-bundler.js:571\nset value @ reactivity.esm-bundler.js:1448\nfinalizeNavigation @ vue-router.mjs:3498\n(anonymous) @ vue-router.mjs:3363\nPromise.then\npushWithRedirect @ vue-router.mjs:3330\npush @ vue-router.mjs:3255\nreplace @ vue-router.mjs:3258\naddRoutes @ virtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:16\n(anonymous) @ virtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:21\n(anonymous) @ client:34\n(anonymous) @ client:208\n(anonymous) @ client:183\nqueueUpdate @ client:183\nawait in queueUpdate\n(anonymous) @ client:884\nhandleMessage @ client:882\nonMessage @ client:299\n(anonymous) @ client:429\ndispatchEvent @ .localservice@runtime.5a421e5b.js:26\n_handleMessage @ .localservice@runtime.5a421e5b.js:26\n_0x3963e2 @ .localservice@runtime.5a421e5b.js:26Understand this warningAI\nruntime-dom.esm-bundler.js:51 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\n at parentNode (runtime-dom.esm-bundler.js:51:30)\n at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js:5410:11)\n at ReactiveEffect.run (reactivity.esm-bundler.js:225:19)\n at ReactiveEffect.runIfDirty (reactivity.esm-bundler.js:263:12)\n at callWithErrorHandling (runtime-core.esm-bundler.js:199:33)\n at flushJobs (runtime-core.esm-bundler.js:408:9)\n```",[2865,2868,2871,2874],{"name":2866,"color":2867},"dx","C39D69",{"name":2869,"color":2870},"bug","d73a4a",{"name":2872,"color":2873},"vite","3574D1",{"name":2875,"color":2876},"馃敤 p3-minor","FBCA04",31493,"nuxt","open","TypeError: Cannot read properties of null (reading 'parentNode') with useFetch","2025-03-21T17:04:23Z","https://github.com/nuxt/nuxt/issues/31493",0.6644207,{"description":2885,"labels":2886,"number":2893,"owner":2878,"repository":2878,"state":2894,"title":2895,"updated_at":2896,"url":2897,"score":2898},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.10.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@4.0.1\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-ktie5u?file=pages%2Fpage-one.vue\n\n### Describe the bug\n\nIf you have 2 different layout and one of them has one child with useAsyncData (or maybe a general fetch?) if you go from the first page with layout `default` to the second page with `another-lyout` and come back, it throw this error: `TypeError: Cannot read properties of null (reading 'parentNode')` and **broke all my website**.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nchunk-ZFKCPPMZ.js?v=9a8b1d1e:1503 [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://github.com/vuejs/core . \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003COther ref=Ref\u003C Proxy(Object)聽{鈥 > > \r\n at \u003CLayoutLoader key=\"other\" layoutProps= {ref: RefImpl} name=\"other\" > \r\n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"other\" name=\"other\" ... > \r\n at \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\nwarn$1 @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1503\r\nlogError @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1709\r\nhandleError @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1701\r\ncallWithErrorHandling @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1653\r\nflushJobs @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1858\r\nPromise.then (async)\r\nqueueFlush @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1767\r\nqueueJob @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1761\r\n(anonymous) @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:7571\r\nresetScheduling @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:513\r\ntriggerEffects @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:557\r\ntriggerRefValue @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1310\r\nset value @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1355\r\nfinalizeNavigation @ vue-router.js?v=3f89114f:2563\r\n(anonymous) @ vue-router.js?v=3f89114f:2473\r\nPromise.then (async)\r\npushWithRedirect @ vue-router.js?v=3f89114f:2441\r\npush @ vue-router.js?v=3f89114f:2367\r\nnavigate @ vue-router.js?v=3f89114f:1621\r\ncallWithErrorHandling @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1651\r\ncallWithAsyncErrorHandling @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1659\r\ninvoker @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:10254\r\nShow 20 more frames\r\nShow less\r\nchunk-ZFKCPPMZ.js?v=9a8b1d1e:9626 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\r\n at parentNode (chunk-ZFKCPPMZ.js?v=9a8b1d1e:9626:30)\r\n at ReactiveEffect.componentUpdateFn [as fn] (chunk-ZFKCPPMZ.js?v=9a8b1d1e:7537:11)\r\n at ReactiveEffect.run (chunk-ZFKCPPMZ.js?v=9a8b1d1e:430:19)\r\n at instance.update (chunk-ZFKCPPMZ.js?v=9a8b1d1e:7577:17)\r\n at callWithErrorHandling (chunk-ZFKCPPMZ.js?v=9a8b1d1e:1651:32)\r\n at flushJobs (chunk-ZFKCPPMZ.js?v=9a8b1d1e:1858:9)\r\nparentNode @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:9626\r\ncomponentUpdateFn @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:7537\r\nrun @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:430\r\ninstance.update @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:7577\r\ncallWithErrorHandling @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1651\r\nflushJobs @ chunk-ZFKCPPMZ.js?v=9a8b1d1e:1858\r\nShow 6 more frames\r\nShow less\n```\n",[2887,2890],{"name":2888,"color":2889},"3.x","29bc7f",{"name":2891,"color":2892},"pending triage","E99695",25694,"closed","Change Layout whit child and useAsync data cannot read 'parentNode'","2024-02-26T14:15:50Z","https://github.com/nuxt/nuxt/issues/25694",0.6231078,{"description":2900,"labels":2901,"number":2907,"owner":2878,"repository":2878,"state":2894,"title":2908,"updated_at":2909,"url":2910,"score":2911},"### Environment\n\nNuxt project info: 15:46:56\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.5.2\r\n- Nitro Version: 2.4.1\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\n[reproduction](https://stackblitz.com/github/jbreuil/layout-repro)\r\n\r\nIn this reproduction, the error is triggered when the layout is changed on routing. The error start appearing when adding a ref element in the component. The ref is on a v-for following the [documentation syntax](https://vuejs.org/guide/essentials/template-refs.html#refs-inside-v-for) and [typing](https://vuejs.org/guide/typescript/composition-api.html#typing-template-refs)\n\n### Describe the bug\n\nRelated to #13309, where people have the same error when using Transition.\r\n\r\nHere the error is the same and triggered at the same time (change of layout on routing to another page). In this reproduction, the error is appearing once we add a ref in the v-for of the component.\r\n\r\nFixed if you downgrade to nuxt 3.3.3\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2902,2903,2904],{"name":2888,"color":2889},{"name":2891,"color":2892},{"name":2905,"color":2906},"upstream","E8A36D",21323,"Layout error when using an Element ref on v-for","2023-07-06T15:39:03Z","https://github.com/nuxt/nuxt/issues/21323",0.62601477,{"labels":2913,"number":2923,"owner":2878,"repository":2878,"state":2894,"title":2924,"updated_at":2925,"url":2926,"score":2927},[2914,2915,2918,2919,2920],{"name":2888,"color":2889},{"name":2916,"color":2917},"workaround available","11376d",{"name":2869,"color":2870},{"name":2905,"color":2906},{"name":2921,"color":2922},"upstream-bug","B60205",13309,"TypeError: Cannot read properties of null (reading 'parentNode')","2025-02-17T17:13:12Z","https://github.com/nuxt/nuxt/issues/13309",0.6326463,{"description":2929,"labels":2930,"number":2934,"owner":2878,"repository":2878,"state":2894,"title":2935,"updated_at":2936,"url":2937,"score":2938},"**reproduction**: https://stackblitz.com/edit/github-cmeky2-mysxox\r\n\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 https://new-issue.vuejs.org/?repo=vuejs/core \r\n at \u003CNuxtRoot>\r\nUncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\r\n```\r\n\r\nContext: https://github.com/nuxt/nuxt.js/issues/13788",[2931,2932,2933],{"name":2888,"color":2889},{"name":2869,"color":2870},{"name":2875,"color":2876},14693,"errors when navigating back and forth from error pages","2023-04-25T15:13:24Z","https://github.com/nuxt/nuxt/issues/14693",0.6381207,{"description":2940,"labels":2941,"number":2945,"owner":2878,"repository":2878,"state":2894,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Environment\r\n\r\nNuxi 3.0.0-rc.12 10:45:12\r\nRootDir: D:/sites/dog-ville-nuxt/dog-ville 10:45:13\r\nNuxt project info: 10:45:13\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.12`\r\n- Nitro Version: `0.6.0`\r\n- Package Manager: `npm@8.15.0`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`, `modules`, `tailwindcss`, `css`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@5.3.5`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nPreviously i was at 11 release candidate. Iam update to new version via changing file package json from\r\n`\"nuxt\": \"3.0.0-rc.11\"` to `\"nuxt\": \"3.0.0-rc.12\"` \r\nAnd execute command npx nuxi@latest cleanup\r\nBefore that everything works fine. After update starts errror\r\n\r\n```\r\n[Vue warn]: injection \"Symbol(route location)\" not found.\r\n[Vue warn]: Unhandled error during execution of render function \r\n at \u003CAnonymous >\r\n[nitro] [dev] [unhandledRejection] TypeError: Cannot read properties of undefined (reading 'meta')\r\nat ReactiveEffect.fn (D:/sites/dog-ville-nuxt/dog-ville/node_modules/nuxt/dist/app/components/layout.mjs:54:106)\r\n```\r\n\r\n### Describe the bug\r\n\r\nIam go to this file and see that this code have this error\r\n```\r\nsetup(props, context) {\r\n const injectedRoute = inject(\"_route\");\r\n const route = injectedRoute === useRoute() ? useVueRouterRoute() : injectedRoute;\r\n const layout = computed(() => unref(props.name) ?? route.meta.layout ?? \"default\");\r\n let vnode;\r\n let _layout;\r\n```\r\nspecific this part route.meta.layout . Iam try to log what is it, something like this\r\n```\r\nsetup(props, context) {\r\n const injectedRoute = inject(\"_route\");\r\n const route = injectedRoute === useRoute() ? useVueRouterRoute() : injectedRoute;\r\n \r\n console.log(1)\r\n console.log(route)\r\n console.log(2)\r\n \r\n const layout = computed(() => unref(props.name) ?? route.meta.layout ?? \"default\");\r\n let vnode;\r\n let _layout;\r\n```\r\nAnd route was undefined. Iam going to different pages and everywhere this error. In more specific, this function is undefined useVueRouterRoute().\r\n \r\nCan somebody help with it?",[2942,2943,2944],{"name":2888,"color":2889},{"name":2869,"color":2870},{"name":2875,"color":2876},15236,"`\u003CNuxtLayout>` does not work without `pages/` integration","2023-01-19T17:46:38Z","https://github.com/nuxt/nuxt/issues/15236",0.6426389,{"description":2951,"labels":2952,"number":2956,"owner":2878,"repository":2878,"state":2894,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.10.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: `yarn@1.22.21`\r\n- Builder: `-`\r\n- User Config: `devtools`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-ghhe2w?file=layouts%2Fdefault.vue\r\n\r\n### Describe the bug\r\n\r\nWhen I clicke the `NuxtLink` text锛宼he browser doesn't to display the pages, and the browser display console the error in the **Logs** section.\r\n\r\n\r\n### Logs\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 https://github.com/vuejs/core . \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\nwarn$1 @ chunk-FRWRVS7C.js?v=373e3ccb:1486\r\n\r\nchunk-FRWRVS7C.js?v=373e3ccb:9605 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\r\n at parentNode (chunk-FRWRVS7C.js?v=373e3ccb:9605:30)\r\n at ReactiveEffect.componentUpdateFn [as fn] (chunk-FRWRVS7C.js?v=373e3ccb:7513:11)\r\n at ReactiveEffect.run (chunk-FRWRVS7C.js?v=373e3ccb:421:19)\r\n at instance.update (chunk-FRWRVS7C.js?v=373e3ccb:7553:17)\r\n at callWithErrorHandling (chunk-FRWRVS7C.js?v=373e3ccb:1634:32)\r\n at flushJobs (chunk-FRWRVS7C.js?v=373e3ccb:1841:9)\r\n```",[2953,2954,2955],{"name":2888,"color":2889},{"name":2916,"color":2917},{"name":2905,"color":2906},25179,"Cannot read properties of null (reading 'parentNode')","2024-07-27T19:16:14Z","https://github.com/nuxt/nuxt/issues/25179",0.6451127,{"description":2962,"labels":2963,"number":2966,"owner":2878,"repository":2878,"state":2894,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v18.12.0\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: devtools, css, build\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nRepo: https://github.com/DiscreteTom/nuxt3-issue\n\n### Describe the bug\n\nI'm using Vuetify with Nuxt. Here is an example `pages/index.vue` to reproduce the bug (see the reproduction repo for the full project code):\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cdiv class=\"d-flex flex-wrap\">\r\n \u003Cv-card\r\n v-for=\"(value, name) in result\"\r\n :key=\"name\"\r\n class=\"mx-2 my-2 flex-grow-1\"\r\n >\r\n \u003Cv-card-title class=\"d-flex align-center\"> \u003C/v-card-title>\r\n \u003Cv-card-text>\r\n {{ value }}\r\n \u003C/v-card-text>\r\n \u003C/v-card>\r\n \u003C/div>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst result = reactive({\r\n key: \"\",\r\n});\r\n\r\nonMounted(() => {\r\n result.key = \"value\";\r\n});\r\n\u003C/script>\r\n```\r\n\r\nWith `ssr: true`, when accessing this page, got the following error:\r\n\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 https://new-issue.vuejs.org/?repo=vuejs/core \r\n at \u003CVCardText> \r\n at \u003CVCard key=\"key\" class=\"mx-2 my-2 flex-grow-1\" > \r\n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C Proxy(Object) > > \r\n at \u003CRouteProvider key=\"/\" vnode= Object route= Object ... > \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CVContainer fluid=\"\" > \r\n at \u003CVMain> \r\n at \u003CVLayout> \r\n at \u003CDefault ref=Ref\u003C Proxy(Object) > > \r\n at \u003CLayoutLoader key=\"default\" layoutProps= Object name=\"default\" > \r\n at \u003CNuxtLayoutProvider layoutProps= Object key=\"default\" name=\"default\" ... > \r\n at \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\n\r\nUncaught (in promise) TypeError: Cannot set properties of null (setting 'nodeValue')\r\n at setText (chunk-BVQHDTV7.js:9152:20)\r\n at processText (chunk-BVQHDTV7.js:6491:9)\r\n at patch (chunk-BVQHDTV7.js:6397:9)\r\n at patchKeyedChildren (chunk-BVQHDTV7.js:7363:9)\r\n at patchChildren (chunk-BVQHDTV7.js:7277:11)\r\n at patchElement (chunk-BVQHDTV7.js:6728:7)\r\n at processElement (chunk-BVQHDTV7.js:6563:7)\r\n at patch (chunk-BVQHDTV7.js:6424:11)\r\n at ReactiveEffect.componentUpdateFn [as fn] (chunk-BVQHDTV7.js:7171:9)\r\n at ReactiveEffect.run (chunk-BVQHDTV7.js:423:19)\r\n```\r\n\r\nEverytime you refresh the page you will get the error message.\n\n### Additional context\n\nThis issue is similiar to https://github.com/nuxt/nuxt/issues/21901 , but seems like not the same.\r\n\r\nThis issue might be caused by universal rendering, which doesn't render the `v-card-text` properly.\r\n\r\nHere are some workarounds I've found:\r\n\r\n- Set `ssr: false`.\r\n- Use `\u003Cclient-only>` to wrap the `\u003Cv-card-text>`.\r\n- Add a placeholder for the `\u003Cv-card-text>`: `{{ value || 'placeholder' }}`\r\n- Change the `\u003Cv-card-text>` to `\u003Cdiv class=\"v-card-text\">`.\n\n### Logs\n\n_No response_",[2964,2965],{"name":2888,"color":2889},{"name":2905,"color":2906},22552,"Unhandled error during execution of scheduler flush. TypeError: Cannot set properties of null (setting 'nodeValue')","2023-08-24T09:35:07Z","https://github.com/nuxt/nuxt/issues/22552",0.6515326,{"labels":2972,"number":2975,"owner":2878,"repository":2878,"state":2894,"title":2976,"updated_at":2977,"url":2978,"score":2979},[2973,2974],{"name":2888,"color":2889},{"name":2891,"color":2892},13285,"Page layout not working as intended","2023-01-19T16:51:10Z","https://github.com/nuxt/nuxt/issues/13285",0.65369546,{"description":2981,"labels":2982,"number":2992,"owner":2878,"repository":2878,"state":2894,"title":2993,"updated_at":2994,"url":2995,"score":2996},"### Environment\r\n\r\n- Operating System: Windows_NT\r\n- Node Version: v20.10.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: pnpm@8.14.1\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n- Vue Version: 3.4.9\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-vhqnzj\r\n\r\n### Describe the bug\r\n\r\nwhen navigate from page with NuxtLayout as root component to another page with NuxtLayout cause TypeError: Cannot read properties of null (reading 'parentNode').\r\nAdding comment above NuxtLayout and still use NuxtLayout as root node doesn't cause this issue (only works in dev mode).\r\nI believe this bug happened after [this](https://github.com/vuejs/core/pull/10055/files#diff-069bd39ee093a8545c4e26aa7264c6ba4561a28f07f3d7d7080f4c0f71710281) specific update in vue v3.4.9\r\n\r\n### Additional context\r\ncondition that's trigger this bug :\r\n- navigate from page with NuxtLayout as root node, to another page with NuxtLayout.\r\n- [#issuecomment-1898592511](https://github.com/nuxt/nuxt/issues/25214#issuecomment-1898592511)\r\n\r\ncondition that's not trigger this bug : \r\n- navigate from page with NuxtLayout as root node, to another page with NuxtLayout and has pageTransition defined.\r\n- navigate from page with NuxtLayout as root node, to another page without NuxtLayout.\r\n\r\n### Logs\r\n\r\n_No response_",[2983,2986,2989,2990,2991],{"name":2984,"color":2985},"documentation","5319e7",{"name":2987,"color":2988},"good first issue","fbca04",{"name":2888,"color":2889},{"name":2916,"color":2917},{"name":2866,"color":2867},25214,"TypeError: Cannot read properties of null (reading 'parentNode') when navigate from page with NuxtLayout as root node","2025-03-21T11:28:32Z","https://github.com/nuxt/nuxt/issues/25214",0.6558574,["Reactive",2998],{},["Set"],["ShallowReactive",3001],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f5y6st70auhrMfG7I8eo0DXntgSQKOT04MMBuXItPFEo":-1},"/nuxt/nuxt/21544"]