\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```",[3020,3023,3026,3029],{"name":3021,"color":3022},"dx","C39D69",{"name":3024,"color":3025},"bug","d73a4a",{"name":3027,"color":3028},"vite","3574D1",{"name":3030,"color":3031},"馃敤 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.6596747,{"description":3040,"labels":3041,"number":3053,"owner":3033,"repository":3033,"state":3054,"title":3055,"updated_at":3056,"url":3057,"score":3058},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.12.1\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nReproduction : https://stackblitz.com/edit/github-88hbfa?file=pages%2Findex.vue\r\n\r\nSteps to reproduce:\r\n1. In a page file, retrieve data using `useAsyncData` and display an array of elements in the template using this data.\r\n2. Assign the array of elements to a ref variable as described in the Vue.js documentation: https://vuejs.org/guide/essentials/template-refs.html#accessing-the-refs.\r\n3. Display this page in a browser.\r\n4. Edit the JS code of this page (e.g., modify console.log).\r\n5. Errors will appear.\r\n\r\nThis error does not occur if:\r\n- The page is being shown for the first time (no reloading through JS edits).\r\n- The code specified above is inside app.vue and not inside a page that is loaded with NuxtPage (if you copy/paste index.vue inside app.vue, errors do not occur).\r\n- No ref is used\r\n- `useAsyncData` is not used\r\n\r\n### Describe the bug\r\n\r\nConsole error is shown related to scheduler flush.\r\nAlso, `TypeError: Cannot read properties of null (reading 'parentNode')` error is thrown.\r\nSee Logs field for more detials about these errors\r\n\r\n### Workarounds\r\n\r\n- Reload page (meh)\r\n- Use `reactive` instead of `ref`\r\n```html\r\n\u003Ctemplate>\r\n\u003Cdiv>\r\n \u003Cli v-for=\"menuItem in menuItems\" ref=\"(el) => updateMenuItemRefs(el)\">\u003C/li>\r\n\u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\n[...]\r\nconst menuItemRefs = reactive([])\r\nfunction updateMenuItemRefs (el) {\r\n menuItemRefs.push(el)\r\n}\r\n\u003C/script>\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n(initially made with `test.vue` page, but error is the same)\r\n\r\n```shell-script\r\ntest.vue:14 edit this message 2\r\n\r\nchunk-3Q27KRJ5.js:97 [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 \u003CRouteProvider key=\"/test\" routeProps= {Component: {鈥, route: {鈥} pageKey=\"/test\" ... > \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\nwarn @ chunk-3Q27KRJ5.js:97\r\nlogError @ chunk-3Q27KRJ5.js:271\r\nhandleError @ chunk-3Q27KRJ5.js:263\r\ncallWithErrorHandling @ chunk-3Q27KRJ5.js:215\r\nflushJobs @ chunk-3Q27KRJ5.js:411\r\nPromise.then (async)\r\nqueueFlush @ chunk-3Q27KRJ5.js:324\r\nqueueJob @ chunk-3Q27KRJ5.js:318\r\nreload @ chunk-3Q27KRJ5.js:517\r\n(anonymous) @ chunk-3Q27KRJ5.js:547\r\n(anonymous) @ test.vue?t=1688346524889:81\r\n(anonymous) @ client.ts:542\r\n(anonymous) @ client.ts:459\r\n(anonymous) @ client.ts:306\r\nqueueUpdate @ client.ts:306\r\nawait in queueUpdate (async)\r\n(anonymous) @ client.ts:159\r\nhandleMessage @ client.ts:157\r\n(anonymous) @ client.ts:90\r\nShow 7 more frames\r\n\r\nchunk-MNWBZQKJ.js:82 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\r\n at parentNode (chunk-MNWBZQKJ.js:82:30)\r\n at ReactiveEffect.componentUpdateFn [as fn] (chunk-3Q27KRJ5.js:5823:11)\r\n at ReactiveEffect.run (reactivity.esm-bundler.js:178:19)\r\n at instance.update (chunk-3Q27KRJ5.js:5860:52)\r\n at callWithErrorHandling (chunk-3Q27KRJ5.js:213:32)\r\n at flushJobs (chunk-3Q27KRJ5.js:411:9)\r\nparentNode @ chunk-MNWBZQKJ.js:82\r\ncomponentUpdateFn @ chunk-3Q27KRJ5.js:5823\r\nrun @ reactivity.esm-bundler.js:178\r\ninstance.update @ chunk-3Q27KRJ5.js:5860\r\ncallWithErrorHandling @ chunk-3Q27KRJ5.js:213\r\nflushJobs @ chunk-3Q27KRJ5.js:411\r\nPromise.then (async)\r\nqueueFlush @ chunk-3Q27KRJ5.js:324\r\nqueueJob @ chunk-3Q27KRJ5.js:318\r\nreload @ chunk-3Q27KRJ5.js:517\r\n(anonymous) @ chunk-3Q27KRJ5.js:547\r\n(anonymous) @ test.vue?t=1688346524889:81\r\n(anonymous) @ client.ts:542\r\n(anonymous) @ client.ts:459\r\n(anonymous) @ client.ts:306\r\nqueueUpdate @ client.ts:306\r\nawait in queueUpdate (async)\r\n(anonymous) @ client.ts:159\r\nhandleMessage @ client.ts:157\r\n(anonymous) @ client.ts:90\r\nShow 8 more frames\r\n```\r\n",[3042,3045,3046,3049,3050],{"name":3043,"color":3044},"3.x","29bc7f",{"name":3024,"color":3025},{"name":3047,"color":3048},"upstream","E8A36D",{"name":3030,"color":3031},{"name":3051,"color":3052},"suspense","C70109",21901,"closed","Unhandled error during execution of scheduler flush related to NuxtPage, useAsyncData & refs ","2024-07-22T19:43:53Z","https://github.com/nuxt/nuxt/issues/21901",0.59308994,{"description":3060,"labels":3061,"number":3065,"owner":3033,"repository":3033,"state":3054,"title":3066,"updated_at":3067,"url":3068,"score":3069},"**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",[3062,3063,3064],{"name":3043,"color":3044},{"name":3024,"color":3025},{"name":3030,"color":3031},14693,"errors when navigating back and forth from error pages","2023-04-25T15:13:24Z","https://github.com/nuxt/nuxt/issues/14693",0.6081642,{"labels":3071,"number":3081,"owner":3033,"repository":3033,"state":3054,"title":3082,"updated_at":3083,"url":3084,"score":3085},[3072,3073,3076,3077,3078],{"name":3043,"color":3044},{"name":3074,"color":3075},"workaround available","11376d",{"name":3024,"color":3025},{"name":3047,"color":3048},{"name":3079,"color":3080},"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.6262612,{"description":3087,"labels":3088,"number":3092,"owner":3033,"repository":3033,"state":3054,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### 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```",[3089,3090,3091],{"name":3043,"color":3044},{"name":3074,"color":3075},{"name":3047,"color":3048},25179,"Cannot read properties of null (reading 'parentNode')","2024-07-27T19:16:14Z","https://github.com/nuxt/nuxt/issues/25179",0.6460243,{"description":3098,"labels":3099,"number":3104,"owner":3033,"repository":3033,"state":3054,"title":3105,"updated_at":3106,"url":3107,"score":3108},"### 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",[3100,3101],{"name":3043,"color":3044},{"name":3102,"color":3103},"pending triage","E99695",25694,"Change Layout whit child and useAsync data cannot read 'parentNode'","2024-02-26T14:15:50Z","https://github.com/nuxt/nuxt/issues/25694",0.64724255,{"description":3110,"labels":3111,"number":3115,"owner":3033,"repository":3033,"state":3054,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.5.3\r\n- Nitro Version: 2.4.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/v-for-layout?file=layouts%2Fdefault.vue\r\n\r\n### Describe the bug\r\n\r\nWhen navigate to a route with a different layout, **and there's a `v-for` with a `ref()`** list inside the page, then return a vue warn and a error.\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]: 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 \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\n\r\n\r\nUncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\r\n at parentNode (chunk-MNWBZQKJ.js:82:30)\r\n at ReactiveEffect.componentUpdateFn [as fn] (chunk-3Q27KRJ5.js:5823:11)\r\n at ReactiveEffect.run (chunk-BOVKDABU.js?v=1765f250:181:19)\r\n at instance.update (chunk-3Q27KRJ5.js:5860:52)\r\n at callWithErrorHandling (chunk-3Q27KRJ5.js:213:32)\r\n at flushJobs (chunk-3Q27KRJ5.js:411:9)\r\n```\r\n",[3112,3113,3114],{"name":3043,"color":3044},{"name":3024,"color":3025},{"name":3030,"color":3031},21544,"v-for doesn't work on change layout","2023-06-23T10:02:04Z","https://github.com/nuxt/nuxt/issues/21544",0.6521503,{"description":3121,"labels":3122,"number":3129,"owner":3033,"repository":3033,"state":3054,"title":3130,"updated_at":3131,"url":3132,"score":3133},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v22.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.1\n- Builder: -\n- User Config: modules, css, ssr, devtools, future, typescript, vite, hooks, nitro, compatibilityDate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, nuxt-mikro-orm-module@0.4.1, @nuxt/eslint@1.0.1, nuxt-auth-utils@0.5.15, @nuxt/image@1.9.0\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nUse this `app.vue`:\n```\n// app.vue\n\u003Cscript setup lang=\"ts\">\n\n\u003C/script>\n\n\u003Ctemplate>\n \u003C!-- https://github.com/nuxt/nuxt/issues/25214#issuecomment-1894051562 -->\n \u003Cdiv>\n \u003CNuxtLoadingIndicator />\n \u003CNuxtRouteAnnouncer />\n\n \u003CNuxtLayout>\n \u003CUApp>\n \u003CNuxtPage />\n \u003C/UApp>\n \u003C/NuxtLayout>\n \u003C/div>\n\u003C/template>\n\n\u003Cstyle>\nbody {\n @apply antialiased;\n background: var(--ui-bg-muted);\n}\n\n.dark {\n body {\n @apply antialiased;\n background: var(--ui-bg);\n }\n}\n\u003C/style>\n```\n\nGo to any page with layout, wait 10-20 sec then try to navigate to another page.\n\n### Describe the bug\n\nSame problem:\nwhen i use navigateTo cant load the page.\nNavigate using user action(navigation menu mouse click) can't load the page\n\n```\n\"nuxt\": \"^3.15.4\",\n\"vue\": \"^3.5.13\",\n\"vue-router\": \"^4.5.0\",\n\"@nuxt/ui\": \"^3.0.0-alpha.10\",\n```\nI get that warning:\n\n\nThen that error:\n\n\nHere is my `app.vue`:\n```\n\u003Cscript setup lang=\"ts\">\n\n\u003C/script>\n\n\u003Ctemplate>\n \u003C!-- https://github.com/nuxt/nuxt/issues/25214#issuecomment-1894051562 -->\n \u003Cdiv>\n \u003CNuxtLoadingIndicator />\n \u003CNuxtRouteAnnouncer />\n\n \u003CNuxtLayout>\n \u003CUApp>\n \u003CNuxtPage />\n \u003C/UApp>\n \u003C/NuxtLayout>\n \u003C/div>\n\u003C/template>\n\n\u003Cstyle>\nbody {\n @apply antialiased;\n background: var(--ui-bg-muted);\n}\n\n.dark {\n body {\n @apply antialiased;\n background: var(--ui-bg);\n }\n}\n\u003C/style>\n```\n\n@TheAlexLichter \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3123,3124,3126],{"name":3102,"color":3103},{"name":3125,"color":3031},"needs reproduction",{"name":3127,"color":3128},"closed-by-bot","ededed",31010,"Unhandled error during execution of component update, Uncaught (in promise) TypeError: node is null","2025-02-28T02:01:44Z","https://github.com/nuxt/nuxt/issues/31010",0.6638193,{"labels":3135,"number":3139,"owner":3033,"repository":3033,"state":3054,"title":3140,"updated_at":3141,"url":3142,"score":3143},[3136,3137,3138],{"name":3043,"color":3044},{"name":3102,"color":3103},{"name":3125,"color":3031},14078,"vue-router error","2023-01-19T17:24:12Z","https://github.com/nuxt/nuxt/issues/14078",0.66665876,{"description":3145,"labels":3146,"number":3150,"owner":3033,"repository":3033,"state":3054,"title":3151,"updated_at":3152,"url":3153,"score":3154},"The recent upgrade to vue 2.5.10 causes hydration errors in my app (commit [4cf855](https://github.com/nuxt/nuxt.js/commit/4cf855ce8115fb17447f2b69fa312237642bbef5)):\r\n\r\n`The client-side rendered virtual DOM tree is not matching server-rendered content.`\r\n\r\nThe error is:\r\n```\r\n[nuxt] Error while initializing app TypeError: Cannot read property 'toLowerCase' of undefined\r\nat emptyNodeAt (vue.runtime.esm.js?ff9b:5127)\r\n...\r\n```\r\n\r\nIt seems that `nodeOps.tagName(elm)` is `undefined`, and that `elm` (if chrome devtools is to be believed) is an empty comment node here:\r\n\r\n```\r\n\u003Cdiv id=\"__nuxt\">\r\n \u003Cdiv class=\"nuxt-progress\" style=\"width:0%;height:2px;background-color:#0275d8;opacity:0;\">\u003C/div>\r\n \u003C!---->\r\n\u003C/div>\r\n```\r\n\r\nAny idea what's going on?\r\n\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/c2071\">#c2071\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3147],{"name":3148,"color":3149},"2.x","d4c5f9",2385,"Latest Vue version update crashes my nuxt app","2023-01-18T15:55:11Z","https://github.com/nuxt/nuxt/issues/2385",0.6716345,["Reactive",3156],{},["Set"],["ShallowReactive",3159],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fnUbnSJjRADEiGgO2APt5IAVF9JBnrKW7Awb5g-AWy4k":-1},"/nuxt/nuxt/22552"]